Piper PA18 accident near Chandler, Arizona, October 24, 2009
On October 24, 2009 at about 4:40 pm local time, a Piper PA18, registered N83281, was substantially damaged in an accident during landing (landing roll) near Chandler, Arizona (Chandler Municipal Airport). 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 failure to maintain directional control while landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 24, 2009 · about 4:40 pm local time
- Place
- Chandler, Arizona · Chandler Municipal Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA18 A150 · all PA18s on the register
- Registration
- N83281 · registry record · serial 18-7609064
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the student pilot, the airplane started to drift to the right as he approached to land, at which time he corrected with left rudder. The student pilot stated, "As the plane touched down it entered a left turn and continued for 270 degrees before coming to a stop just off the runway." A postaccident examination revealed that the right wing had sustained substantial damage as a result of impact with terrain. The pilot reported no mechanical failures or malfunctions with the airplane at the time of the accident.
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
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
- Runway excursion 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: 26 hours in all; 26 in this make and model; 26 in the last 90 days; 14 in the last 30 days; 3 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: frt
- Injury: no injuries
The aircraft
- Last inspection: annual inspection, September 4, 2009; 56 hours since
- Maximum gross weight: 1,750 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320 (piston); 0 hours total
- Operator: Chandler Air Service Inc.
The flight
- Departed from: CHD Chandler AZ at 4:00 pm
- Destination: CHD Chandler AZ
- Flight plan: none
- Runway 04R, 4,400 ft by 75 ft
Weather at the time
- Light: daylight
- Visibility: 40 statute miles
- Sky: a few clouds at 18,000 ft
- Temperature: 64°F (18°C), dew point 34°F (1°C)
- Altimeter: 29.95 inHg
- Observation at 4:47 pm from CHD
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.
