MIA91FA160 · Piper PA38-112
Bay Aviation Piper PA38-112 · Accident: in flight collision with object en route
From PFN · Panama City, FL to an unrecorded destination
Event
- NTSB case
- MIA91FA160
- 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
Piper PA38-112
- Aircraft type
- Piper PA38
- 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
- N2549A
- Operator
- Bay Aviation
- Onboard fatalities
- Unknown
- Route
- From PFN · Panama City, 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
- 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
- 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
- Wire, transmission
- 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 › Altitude, improper
- Pilot in command › Overconfidence in personal ability
- Pilot in command › Visual lookout, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
FLIGHT COLLIDED WITH TOP WIRES OF ELECTRICAL TRANSMISSION LINES WHICH CROSSED A LAKE. POST CRASH EXAMINATION OF THE AIRCRAFT, FLIGHT CONTROLS, AND ENGINE REVEALED NO EVIDENCE TO INDICATE PRECRASH FAILURE OR MALFUNCTION. AT THE TIME OF THE ACCIDENT THE STUDENT PILOT WAS ON A SOLO INSTRUCTIONAL FLIGHT OPERATING IN A DESIGNATED PRACTICE AREA 15 MILES NORTH OF THE DEPARTURE AIRPORT.
Probable cause
THE PILOT IN COMMANDS FAILURE TO MAINTAIN A SAFE ALTITUDE RESULTING IN AN INFLIGHT COLLISION WITH ELECTRICAL LINES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA91FA160
- Event ID
- 20001212X17334
- Case number
- MIA91FA160
- 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: eb885593a7bac5be44a971a22bd3a0adf86341d66fc33c31216d918084e53256; retrieved 2026-09-21T01:47:07.822Z.