ATL85IA251 · Cessna 441
Cessna 441 · Incident: loss of control on ground/water during landing
From Detroit, MI to an unrecorded destination
Event
- NTSB case
- ATL85IA251
- 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
- Incident
- 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 441
- Aircraft type
- Cessna 441
- 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
- N2624D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Detroit, MITo 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 · landing roll
- 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
- Loss of control on ground/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
- Propeller governor control › Asymmetrical
- Propeller system/accessories › Improper
- Throttle/power lever › Improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT THE APPROACH SEQUENCE AND PROFILE WERE NORMAL, AND THERE WERE NO APPARENT AIRCRAFT PROBLEMS. AFTER TOUCH DOWN THE PILOT APPLIED REVERSE THRUST. DURING THE LANDING ROLL OUT, THE AIRCRAFT VEERED OFF THE LEFT SIDE OF THE RUNWAY, COLLIDED WITH A TAXIWAY MARKER AND A RUNWAY LIGHT. THE AIRCRAFT EXAMINATION DISCLOSED THAT, THE LEFT PROPELLER GROUND STRIKE HAD OCCURRED. WHEN PULLED INTO REVERSE, THE THROTTLE LEVERS COULD OVERLAP, CAUSING A DIFFERENCE IN THE FUEL CONTROLLER READING ON EACH ENGINE. THE ENGINE EXAMINATION DISCLOSED THAT THE RIGHT ENGINE NEGATIVE TORQUE SENSING CAMSET WAS DISPLACED TWO TEETH FROM THE INSTALLED REFERENCE POINT. THIS CONDITION PREVENTED THE RIGHT PROPELLER FROM COMING OUT OF THE FEATHER POSITION DURING THE POST INCIDENT EXAMINATION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL85IA251
- Event ID
- 20001214X37356
- Case number
- ATL85IA251
- 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: dd66e38869562ff0313131de9cb4326a1723f3dcf0c36fa26fcff6f206759f57; retrieved 2026-09-23T16:15:16.404Z.