FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04LA247 · Cessna 150M

10 Dec 2003 · Tucson, AZ, United States

International Airline Training Academy Cessna 150M · Accident: hard landing

From Ryan Field (RYN) to Ryan Field (RYN)

Report a problem

Event

NTSB case
LAX04LA247
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 150M

Aircraft type
Cessna 150
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
N63149
Onboard fatalities
Unknown
Route
From Ryan Field (RYN), Tucson, AZTo Ryan Field (RYN), Tucson, AZ
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, misjudged
  • Pilot in command › Porpoise/pilot-induced oscillation, inadvertent
  • Pilot in command › Recovery from bounced landing, 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 airplane landed hard and porpoised down the runway. During the landing, the pilot began his flare 1/3 of the way down the runway. The airplane's approach speed was slightly high and the flare was longer than the pilot expected. When he was halfway down the runway, he further raised the airplane's nose to land. The pilot realized that he was too high for a normal touchdown and was also slow. The airplane landed hard and bounced three times before the nose wheel collapsed.

Probable cause

the pilot's misjudged flare and improper recovery from a bounced landing, which resulted in a pilot induced porpoise/oscillation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04LA247
Event ID
20040712X00951
Case number
LAX04LA247
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: 66778e41e5d9fef3f10d189914a23beb6f52ac907657d11830c143cbd4cbabfc; retrieved 2026-09-22T08:05:32.185Z.