Tampa Airways Cessna 210M accident
Cessna 210M · Accident: total loss of engine power (non-mechanical) on approach
From Tampa International Airport (TPA) to Jacksonville Executive at Craig Airport (CRG)
Event
- NTSB case
- MIA88FA012
- 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
- Charter & commuter
- 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 210M
- Aircraft type
- Cessna 210
- 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
- N8193M
- Operator
- Tampa Airways
- Onboard fatalities
- Unknown
- Route
- From Tampa International Airport (TPA), Tampa, FLTo 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 135: Air Taxi & Commuter
- 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
- Approach
- 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 (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Fluid, oil › Exhaustion
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A PART 135 ON-DEMAND AIR TAXI CARGO FLT, THE PLT REPORTED AN ENG MALFUNCTION WHEN THE ACFT WAS APRX 15 MILES SW OF THE ARPT WHILE ON APCH TO LAND. THE FLT CONTINUED & THE PLT THEN REPORTED THAT THE ENG QUIT & THE FLT WAS 5 MILES SW OF THE ARPT. A SEARCH & RESCUE HELICOPTER WHICH HAD JUST LANDED AT THE ARPT FLEW TOWARDS THE ACFT TO OFFER ASSISTANCE, & DUE TO THE DARK NIGHT CONDITION SPOTTED & GUIDED IT TOWARDS A SUITABLE LANDING LOCATION. WHILE DESCENDING THE ACFT FLEW BETWEEN TWO TREES WHICH SEVERED A 1 1/2 FT SECTION OF EACH WINGTIP. AS THE ACFT CONTINUED THE LEFT WING COLLIDED WITH A TREE. THE ACFT SPUN TO THE LEFT AND COLLIDED WITH TERRAIN. AFTER THE PLT EVACUATED THE ACFT, IT WAS CONSUMED BY POSTCRASH FIRE. POSTCRASH EXAM OF THE ENG REVEALED THAT IT SEIZED DUE TO OIL EXHAUSTION. NO DETERMINATION COULD BE MADE AS TO THE REASON FOR OIL EXHAUSTION. EVIDENCE OF OIL LEAKAGE WAS FOUND ON THE FUSELAGE BUT NO SOURCE OF THE LEAK WAS FOUND. THE OIL FILLER CAP WAS FOUND PROPERLY SECURED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA88FA012
- Event ID
- 20001213X32384
- Case number
- MIA88FA012
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1987-10-21.
- API snapshot SHA-256: f03303b1811e8873b89ed1b7d37afeca6988288761a3c33142ed1ef170d83764; retrieved 2026-09-18T19:36:35.480Z.