FTW84LA202 · Cessna 500
Cessna 500 · Accident: in flight collision with terrain/water during landing
Event
- NTSB case
- FTW84LA202
- 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 500
- Aircraft type
- Cessna 500
- 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
- N92FA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- In flight collision with terrain/water
- 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
- Check pilot › Supervision, inadequate
- Pilot in command › Gear extension, not performed
- Pilot in command › Wheels up landing, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A PROFICIENCY FLT CHECK, THE AIRCREW WAS MAKING A N0-FLAP LANDING. AFTER COMPLETING THE LANDING CHECKLIST DOWN TO THE LANDING GEAR, POWER WAS REDUCED CAUSING THE LANDING GEAR AUDIBLE WARNING TO SOUND. THE HORN SILENCE SWITCH WAS DEPRESSED & THE APCH WAS CONTINUED. DUE TO THE LOW POWER THAT WAS REQUIRED FOR THE NO-FLAP APCH, THE THROTTLE WAS NEVER ADVANCED SUFFICIENTLY TO RESET THE WARNING HORN. SUBSEQUENTLY, THE ACFT WAS LANDED WITH THE GEAR RETRACTED. AFTER SLIDING TO A STOP, A SMALL ELECTRICAL FIRE ERUPTED IN THE BELLY OF THE ACFT, BUT ARPT PERSONNEL QUICKLY EXTINGUISHED IT. THE PLT BEING CHECKED SAID HE WAS DISTRACTED BY A CONVERSATION CONCERNING ENG FIRE PROCEDURES. ALSO, HE THOUGHT THE CHECK PLT HAD CALLED THAT THE LANDING CHECK WAS COMPLETE. THE CHECK PLT STATED THAT HE HAD CALLED ONLY THE NO-FLAP CHECKLIST COMPLETE WITH THE BEFORE LANDING CHECKLIST COMPLETE DOWN TO THE LANDING GEAR. THE PROFICIENCY FLT WAS BEGUN ON A SHORT NOTICE WHEN ANOTHER CHECK PLT COULD NOT BE FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW84LA202
- Event ID
- 20001214X39280
- Case number
- FTW84LA202
- 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: e63e36c87bb74db2ddb713f4b9cc13a6cba35b341f3287b4325439947ee02787; retrieved 2026-09-23T20:36:50.492Z.