Piper PA-28-180 accident near Springerville, Arizona, November 23, 2006
On November 23, 2006 at about 1:55 am local time, a Piper PA-28-180, registered N4925L, was substantially damaged in an accident near Springerville, Arizona (Springerville Municipal airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
the pilot's inadequate compensation for the crosswind condition and failure to maintain directional control during landing. A factor was the crosswind.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 23, 2006 · about 1:55 am local time
- Place
- Springerville, Arizona · Springerville Municipal · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-180 · all PA-28-180s on the register
- Registration
- N4925L · no longer on the register · serial 28-4291
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane veered off the runway 11, an asphalt surface that was 4,589 feet long and 60 feet wide, and collapsed the landing gear during a night landing. The weather conditions recorded at nearby airports indicated that a slight crosswind situation likely existed. According to the pilot, he was established on final approach when he noticed the airplane drifting to the right of centerline. He maneuvered the airplane into a sideslip to the left. The airplane touched down on the left main landing gear first, then it suddenly veered off the runway surface to the left. The pilot added power and pulled up on the nose in an attempt to soften the rollout; however, the landing gear collapsed and the airplane skidded to a stop. The pilot reported no mechanical problems with the airplane prior to the event.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 85 hours in all; 56 in this make and model; 2 in the last 90 days; 22 as pilot in command
- Last flight review: November 1, 2005
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 5,166.9 hours
- Last inspection: annual inspection, February 1, 2006; 91.3 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360-A4A (piston); 0 hours total
The flight
- Departed from: SAD Safford AZ at 1:03 am
- Destination: D68 Springerville AZ
- Flight plan: none
- Runway 11, 4,589 ft by 60 ft
Weather at the time
- Light: night, dark
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 54°F (12°C), dew point 18°F (-8°C)
- Altimeter: 30.23 inHg
- Observation at 1:54 am from SJN, 24 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.