SEA03LA172 · Cessna 152
Cessna 152 · Accident: hard landing
From 6S5 · Hamilton, MT to 6S5 · Hamilton, MT
Event
- NTSB case
- SEA03LA172
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 152
- Aircraft type
- Cessna 152
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N68281
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 6S5 · Hamilton, MTTo 6S5 · Hamilton, MT
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Flare, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot said his airspeed was a little faster than he would normally use as the aircraft touched down on its main landing gear and bounced. On the second contact with the runway he applied back pressure on the yoke and it bounced again, about 12 feet high. Prior to the third bounce, the pilot again applied back pressure on the control yoke causing it to bounce high again. As the airplane was now going too slow, the pilot felt that adding power would only make the problem worse. The airplane contacted the runway the fourth time with all three landing gear, causing the nose gear to buckle, impacting the firewall. The aircraft came to rest on its nose and left wing with the tail projecting 45 degrees into the air. The pilot reported that no power was added for recovery in spite of his prior instruction and practice in hard landing recovery. Post-accident examination of the aircraft revealed damage to the firewall and left wing.
Probable cause
The student pilot's improper flare which resulted in a hard landing. A factor was the improper recovery from the bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03LA172
- Event ID
- 20030903X01444
- Case number
- SEA03LA172
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 52ce0e574c97bcfd896ef2c3f15dbceb7e96fbe8dd4f8fbcf2aedd773a714e4d; retrieved 2026-09-22T08:44:26.893Z.