MIA92FA058 · Cessna 402B
Cessna 402B · Accident: total loss of engine power (mechanical failure) en route
From an unrecorded airport to Jacksonville Executive at Craig Airport (CRG)
Event
- NTSB case
- MIA92FA058
- 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
- 1 · 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 402B
- Aircraft type
- Cessna 402
- 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
- N3767C
- Operator
- Charles M. Howell III · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, FL
- 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
- En route · cruise
- 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
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed(vmc), not maintained
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Planned approach, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
FLT DEPARTED AND UPON REACHING A POINT APPROX 35 MILES NORTH OF ARPT PLT REQUESTED RETURN TO ARPT FROM ATC. PLT DID NOT DECLARE EMERGENCY OR REPORT AN ENGINE PROBLEM. UPON ENTERING TRAFFIC PATTERN AT UNCONTROLLED ARPT PLT STATED HE WOULD FOLLOW A CESSNA 152 FOR LANDING. ON SHORT FINAL ACFT WAS SEEN MAKING S TURNS TO MAINTAIN SPACING BEHIND 152. PLT THEN DECLARED HE HAD AN ENGINE SHUTDOWN AND NEEDED TO LAND. 152 WAS IN LANDING FLARE AND LANDED. WITH 152 ON RUNWAY PLT ATTEMPTED A GO AROUND WITH FULL FLAPS EXTENDED, GEAR DOWN, LEFT ENG SHUTDOWN, AND AT A SLOW AIRSPEED. ACFT ROLLED TO LEFT UPON APPLICATION OF RIGHT ENG POWER AND NOSED DOWN FROM WHICH IT CRASHED. THE NUMBER TWO CYLINDER OF THE LEFT ENG HAD SUFFERED SEPARATION OF THE HEAD FROM THE BARREL. PLT LOGBOOK DID NOT REFLECT PLT HAVING CURRENT BIENNIAL FLT REVIEW.
Probable cause
THE PILOT IN COMMANDS FAILURE TO MAINTAIN AIRSPEED ABOVE SINGLE ENGINE MINIMUM CONTROL SPEED RESULTING IN AN INFLIGHT LOSS OF CONTROL AND COLLISION WITH TERRAIN. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT IN COMMAND'S FAILURE TO DECLARE AN EMERGENCY AND REQUEST PRIORITY LANDING AND HIS DECISION TO FOLLOW A SLOWER AIRCRAFT IN THE PATTERN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA92FA058
- Event ID
- 20001211X14023
- Case number
- MIA92FA058
- 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: 6f4a74f54d0dcc4c421c6bdde98a3d84e5f3b7d79ef79131d3c8b62cc5fad3bb; retrieved 2026-09-21T01:24:52.136Z.