MIA84FA092 · Piper PA-30
Piper PA-30 · Accident: loss of control in flight during initial climb
From an unrecorded airport to Northeast Florida Regional Airport (SGJ)
Event
- NTSB case
- MIA84FA092
- 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
- 3 · 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
Piper PA-30
- Aircraft type
- Piper PA-30
- 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
- N710SC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Northeast Florida Regional Airport (SGJ), ST.AUGUSTINE, 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
- Initial climb
- 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 in flight
- 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
- Stall; Wire, static; 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 › Airspeed(vs), not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF THE ACFT ENTERED A DESCENDING LEFT TURN, STRUCK A WIRE, A CAR, AND A TREE BEFORE CONTACTING A BUILDING AND EXPLODING. A PASSENGER REPORTED THAT THE STALL WARNING HORN HAD ACTIVATED AT LEAST TWICE DURING THE INITIAL TAKEOFF CLIMB PRIOR TO THE ACFT ENTERING THE LEFT DESCENDING TURN. WITHIN SECONDS AFTER CONTACTING THE BUILDING THE ACFT EXPLODED. INVESTIGATION REVEALED THERE WAS APRX 3600 FT OF USABLE RWY AVAILABLE AT THE POINT OF THE INTERSECTION TAKEOFF WHICH WAS REQUESTED BY THE PLT. WEIGHT AND BALANCE CALCULATIONS INDICATE THE ACFT WAS APRX 172 LBS OVER MAX GROSS WEIGHT AT TAKEOFF. NO MECHANICAL FAILURE/MALFUNCTION WAS FOUND DURING THE INVESTIGATION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA84FA092
- Event ID
- 20001214X38847
- Case number
- MIA84FA092
- 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: e201a2a82e24792c883b33c510faad7fe9068f9ca89fb55345da3359170ace50; retrieved 2026-09-21T05:38:39.536Z.