Cessna 152 accident near Kelso, Washington, February 19, 2013
On February 19, 2013 at about 9:40 pm local time, a Cessna 152, registered N89956, was substantially damaged in an accident during landing (flare/touchdown) near Kelso, Washington (Southwest Washington Regional 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 inadequate landing flare and lack of remedial actions, which resulted in a hard bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 19, 2013 · about 9:40 pm local time
- Place
- Kelso, Washington · Southwest Washington Regional · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 152 · all 152s on the register
- Registration
- N89956 · no longer on the register · serial 15282927
- 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 he reduced engine power while on final approach and that the airplane developed a higher sink rate than expected. The airplane subsequently landed hard and bounced three to four times, collapsing the nose landing gear and substantially damaging the firewall. The student pilot stated that he did not attempt to go around. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
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
- Hard landing during landing (flare/touchdown) defining event
- Loss of control on ground during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Student pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
Dual student
- Certificate: student
- Flight time: 46 hours in all; 46 in this make and model; 24 in the last 90 days; 9 in the last 30 days; 3 as pilot in command
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-235-L2C (piston); 0 hours total
- Operator: Hillsboro Aviation INC
The flight
- Departed from: DLS The Dalles OR at 8:15 pm
- Destination: KLS Kelso WA
- Flight plan: VFR
- Runway 12, 4,391 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
- Observation at 9:35 pm from KLS
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.