MIA87LA039 · Navion H
Navion H · Accident: airframe, component or system failure en route
From St. Petersburg Clearwater International Airport (PIE) to Boca Raton Airport (BCT)
Event
- NTSB case
- MIA87LA039
- 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
Navion H
- Aircraft type
- Navion H
- 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
- N2507T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St. Petersburg Clearwater International Airport (PIE), ST.PETERSBURG, FLTo Boca Raton Airport (BCT), Boca Raton, 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
- Airframe, component or system failure
- 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
- Fuel starvation
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Estimated position: the centre of Fort Pierce, FL, the place the record names. Not the accident site.
NTSB narrative
THE PLT STATED THAT WHILE EN ROUTE TO BOCA RATON, FL, HE EXPERIENCED COMPLETE ELECTRICAL FAILURE NEAR LABELLE, FL. HE CONTINUED INBOUND BUT WHEN IN THE BOCA RATON AREA, ENCOUNTERED OTHER TRAFFIC AND BECAUSE OF THE CONGESTION DECIDED TO FLY NORTH ALONG THE COAST BUT ENCOUNTERED MORE TRAFFIC IN THE WEST PALM BEACH AND STUART AREA. STILL HEADING NORTHBOUND HE TRIED SWITCH TANKS TO TRANSFER FUEL. THE ENGINE QUIT AND WOULD NOT RESTART BECAUSE THERE WAS NO ELECTRICAL POWER TO RUN THE BOOST PUMP, SO HE DITCHED THE AIRCRAFT IN THE INDIAN RIVER NEAR FT. PIERCE, FL. POST CRASH EXAMINATION OF THE ELECTRICAL SYSTEM REVEALED THAT THE VOLTAGE REGULATOR WAS INOPERATIVE WHICH RESULTED IN THE ELECTRICAL FAILURE EXPERIENCED BY THE PLT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA87LA039
- Event ID
- 20001213X35234
- Case number
- MIA87LA039
- 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: 8f2304ad5e2fc69a5d2ad4610b79dd0ebc5add03c448d34e91f49822c37b55db; retrieved 2026-09-21T16:48:48.743Z.