MIA93FA036 · Piper PA-28R-200
Piper PA-28R-200 · Accident: in flight collision with object on approach
From Jacksonville International Airport (JAX) to X41 · New Port Richey East, FL
Event
- NTSB case
- MIA93FA036
- 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
- Instrument Meteorological Cond
Piper PA-28R-200
- Aircraft type
- Piper PA-28
- 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
- N5343T
- Operator
- King, Russell S. · private individual
- Onboard fatalities
- Unknown
- Route
- From Jacksonville International Airport (JAX), Jacksonville, FLTo X41 · New Port Richey East, 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
- 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
- Wire, static
- 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 › Minimum descent altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING HIS WX BRIEFING BEFORE FLIGHT, THE PLT DID NOT REQUEST PUBLISHED NOTAM INFORMATION WHICH WOULD HAVE ADVISED HIM THAT THE VOR APCH TO THE DESTINATION ARPT WAS NOT AUTHORIZED. UPON ARRIVING IN THE VICINITY OF THE DESTINATION, THE PILOT WAS RADAR VECTORED AND THEN CLEARED FOR THE VOR-A APPROACH. IN RESPONSE TO THE CONTROLLER'S QUERY ABOUT RECEIVING THE VOR, THE PLT STATED 'GOT IT.' THE LAST RADAR RETURN SHOWED THE AIRPLANE AT 200 FT. THE AIRPLANE COLLIDED WITH A POWER LINE SAFETY CABLE APRX 115 FT AGL. THE VOR-A APPROACH HAD BEEN NOTAMED AS BEING NOT AUTHORIZED BECAUSE A FLIGHT CHECK SHOWED THE APPROACH RADIAL AS BEING ROUGH WITH SCALLOPING. THE MINIMUM DESCENT ALTITUDE WAS 680 FT.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN THE MINUMUM DESCENT ALTITUDE (MDA) WHILE ON A NON-PRECISION INSTRUMENT APPROACH. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE: THE FLIGHT SERVICE STATION (FSS) SPECIALIST'S FAILURE TO PROVIDE THE PUBLISHED NOTICE TO AIRMEN (NOTAM) INFORMATION TO THE PILOT DURING THE WEATHER BRIEFING, AND THE CONTROLLER'S FAILURE TO REMEMBER THAT THE VOR-A APPROACH WAS NOT AUTHORIZED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA93FA036
- Event ID
- 20001211X16203
- Case number
- MIA93FA036
- 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: ef98d628b3d0eb3e3f4e2e24627ee642792faf4f5e22d093191cb62dcd57738d; retrieved 2026-09-21T00:45:25.474Z.