Piper PA-28-181 accident near Mesa, Arizona, August 19, 2009
On August 19, 2009 at about 9:36 pm local time, a Piper PA-28-181, registered N4177L, was substantially damaged in an accident during landing (landing roll) near Mesa, Arizona (Falcon Field). It was an instructional 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 student pilot’s inadequate compensation for the crosswind condition and failure to maintain directional control during landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 19, 2009 · about 9:36 pm local time
- Place
- Mesa, Arizona · Falcon Field · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-181 · all PA-28-181s on the register
- Registration
- N4177L · registry record · serial 2843210
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot reported that during a crosswind landing just prior to the airplane’s nose wheel touching down, the airplane’s right wing rose and the airplane began to veer to the left. The airplane exited the runway to the left, impacted a runway sign, and ground looped. Examination of the airplane revealed structural damage to the left main landing gear strut and the horizontal stabilizer. The pilot said there were no preimpact mechanical malfunctions or failures.
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
What happened, in order
- Loss of control on ground during landing (landing roll) defining event
- Runway excursion during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
Dual student
- Certificate: student
- Flight time: 31 hours in all; 31 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 14,500 hours
- Last inspection: 100-hour inspection, August 3, 2009
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-360-A1D (piston); 0 hours total
- Operator: Sabena Airline Training Center, INC.
The flight
- Departed from: FFZ Mesa AZ at 8:45 pm
- Destination: FFZ Mesa AZ
- Flight plan: none
- Runway 22L, 5,101 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 240° at 15 knots
- Visibility: 40 statute miles
- Sky: clear
- Temperature: 102°F (39°C), dew point 50°F (10°C)
- Altimeter: 29.79 inHg
- Observation at 9:56 pm from KFFZ
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight 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.