FTW90LA182 · Cessna 150M
Cessna 150M · Accident: hard landing
From F67 · Grand Prairie, TX to F54
Event
- NTSB case
- FTW90LA182
- 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
- 0
- 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
- N66689
- Operator
- Cameron, Marcus R. · private individual
- Onboard fatalities
- Unknown
- Route
- From F67 · Grand Prairie, TXTo F54
- 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
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT STATED THAT AFTER A NORMAL APPROACH AND LANDING, HE EXPERIENCED A NOSE WHEEL SHIMMY AND THE AIRPLANE PULLED TO THE LEFT. HE STATED THAT HIS ATTEMPTS TO RAISE THE NOSE WHEEL OFF OF THE RUNWAY RESULTED IN THE AIRPLANE BECOMING AIRBORNE ONCE OR TWICE, AND THAT ON THE SECOND OR THIRD TOUCHDOWN THE NOSE GEAR COLLAPSED. HE SAID THE AIRPLANE HAD A HISTORY OF NOSE WHEEL SHIMMY AND THAT IT HAD OCCURRED ON THE PREVIOUS TAKEOF. A CFI WHO OBSERVED THE ACCIDENT SAID THE APPROACH WAS NORMAL BUT, INSTEAD OF FLARING, THE AIRPLANE NOSED DOWN AND HIT THE RUNWAY IN A 'CLASSIC WHEELBARROW NOSE WHEEL FIRST CONFIGURATION.' THE THEN SAW THE AIRPLANE BOUNCE AND COME DOWN ON THE NOSE A SECOND TIME AND THE NOSE GEAR COLLAPSED. NO EVIDENCE OF PRE-IMPACT FAILURE OR MALFUNCTION WAS FOUND AND THE OPERATOR'S RECORDS DID NOT INDICATE A HISTORY OF NOSE GEAR SHIMMY.
Probable cause
THE PILOT'S FAILURE TO PROPERLY FLARE THE AIRPLANE FOR LANDING AND HIS FAILURE TO INITIATE THE PROPER RECOVERY PROCEDURES FOLLOWING THE BOUNCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90LA182
- Event ID
- 20001212X24277
- Case number
- FTW90LA182
- 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. 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: 6e4d69e66e4b3712ac8804593807362685ff99f87ddeddb1cf5a5674e7c0afac; retrieved 2026-09-23T05:17:02.806Z.