FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA86MA057 · Piper PA-31T

9 Jan 1986 · Jacksonville, FL, United States

Peachtree City Leasing Piper PA-31T · Accident: in flight collision with object on approach

From 4AZ · Hampton, GA to Jacksonville International Airport (JAX)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
MIA86MA057
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

Piper PA-31T

Aircraft type
Piper PA-31
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
N700CM
Onboard fatalities
Unknown
Route
From 4AZ · Hampton, GATo Jacksonville International Airport (JAX), Jacksonville, 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
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 › Decision height, improper use of
  • Pilot in command › Descent, excessive
  • Pilot in command › Missed approach, not performed
  • Pilot in command › Planned approach, improper use of

Approximate · Estimated position: the centre of Jacksonville, FL, the place the record names. Not the accident site.

NTSB narrative

WHILE BEING VECTORED FOR AN ILS RWY 7 APCH, THE PLT WAS TOLD TO MAINT 3000' & ADVISED HE WAS FLWG A BOEING 727. THE MIN APCH ALT BFR INTERCEPTING THE ILS GLIDE SLOPE (G/S) AT THE FINAL APCH FIX/OUTER MARKER (OM) WAS 1900'. AS THE ACFT WAS APCHG THE OM, THE PLT WAS CLRD FOR THE APCH & WAS HANDED OFF TO THE TWR. AFTER CONTACTING THE TWR, THE PLT WAS TOLD TO DSCND AS PUBLISHED. AT APRX THAT TIME, THE TWR CONTROLLER (CTLR) & HIS SUPERVISOR DISCUSSED N700CM'S ALT & PROXIMITY TO THE 727. THE CTLR WAS GOING TO DISCONTINUE THE APCH, BUT HIS SUPVR SUGGESTED HE WAIT & SEE IF IT WOULD WORK OUT. SUBSEQUENTLY, N700CM CRASHED INTO TREES APRX 5800' SHORT OF THE RWY WHILE DSCNDG IN A WINGS LVL ATTITUDE. RADAR DATA SHOWED N700CM WAS WELL ABV THE ILS G/S WHEN CLRD FOR THE APCH. ATC PROCEDURES REQD THE ACFT TO BE BLO THE G/S BFR BEING CLRD. ALSO, N700CM WAS APRX 2.57 MI BEHIND THE 727, BUT STAYED WELL ABV THE 727'S FLT PATH (& POSSIBLE WAKE TURBULENCE) UNTIL MOMENTS BFR IMPACT. N700CM ENTERED AN EXCESSIVE RATE OF DSCNT BFR GOING BLO THE G/S.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MIA86MA057
Event ID
20010110X00227
Case number
MIA86MA057
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1986-01-10.
  • API snapshot SHA-256: 15200dfc6444414b620bd0bf682302f32d90141513fd269bb6827636d729d722; retrieved 2026-09-21T04:42:25.465Z.