MIA92GA107 · Beech C90
State of Florida Beech C90 · Accident: in flight collision with object on approach
From THL · Tallahassee, FL to an unrecorded destination
Event
- NTSB case
- MIA92GA107
- 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
- 2 · 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
- Instrument Meteorological Cond
Beech C90
- Aircraft type
- Beechcraft 90
- 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
- N105FL
- Operator
- State of Florida
- Onboard fatalities
- Unknown
- Route
- From THL · Tallahassee, FLTo 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
- Approach · IFR final 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
- In flight collision with object
- 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
- Pilot in command › IFR procedure, improper
Approximate · Estimated position: the centre of Saint Augustine, FL, the place the record names. Not the accident site.
NTSB narrative
THE AIRPLANE DISAPPEARED FROM RADAR ABOUT 1-1/2 MI SHORT OF THE AIRPORT DURING A VOR RUNWAY 13 APPROACH. RADAR DATA SHOWS THAT THE ALTITUDES, DESCENT RATES, AND GROUND SPEEDS WERE CONSISTENT WITH THE APPROACH PROFILE. THE LAST RADAR POSITION OF THE AIRPLANE WAS AT 100 FT ON THE RUNWAY EXTENDED CENTERLINE. THE DEBRIS PATH WAS ALIGNED ON A 130 DEG MAG HEADING. WITNESSES STATED THAT THE VISIBILITY WAS NEAR ZERO IN FOG.
Probable cause
THE PILOT'S FAILURE TO PROPERLY ADHERE TO THE PUBLISHED INSTRUMENT APPROACH PROCEDURE WHICH RESULTED IN DESCENT BELOW THE MINIMUM DESCENT ALTITUDE. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE THE LOW CEILING AND FOG.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA92GA107
- Event ID
- 20001211X14478
- Case number
- MIA92GA107
- 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: e1a8546bea3e70cc1d0090cc64747d06c6a042583763843c619d46163125ac22; retrieved 2026-09-21T01:16:40.500Z.