NYC84FA163 · Cessna 310K
Cessna 310K · Accident: in flight collision with object on approach
From Philadelphia International Airport (PHL) to Harrisburg International Airport (MDT)
Event
- NTSB case
- NYC84FA163
- 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
- 1
- 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
Cessna 310K
- Aircraft type
- Cessna 310
- 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
- N6907L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Philadelphia International Airport (PHL), Philadelphia, PATo Harrisburg International Airport (MDT), Middletown, PA
- 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); 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 › Clearance, not maintained
- Pilot in command › IFR procedure, not followed
- Pilot in command › Lack of total experience in type of aircraft
- Pilot in command › Lack of total instrument time
- Pilot in command › Underconfidence in personal ability
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT DEPARTED VFR WITHOUT A FORMAL WX BRIEFING OR FILING A FLT PLAN. THE WX AT DEST WAS VFR WHEN THE PLT DEPARTED. THE FORECAST INDICATED THAT CEILINGS WOULD LOWER. THE WX DID, IN FACT, DETERIORATE WHILE THE FLT WAS ENROUTE AND THE PLT OBTAINED AN IFR CLEARANCE. ATC NOTED THE PLT MAKING ERRATIC RIGHT & LEFT TURNS AND QUERIED THE PLT WHO RESPONDED THEAT 'EVERYTHING WAS FINE'. LATER, THE PLT WAS OBSERVED BY CONTROLLERS ON THE APPRCH HAVING DIFFICULTY NAVIGATION. AGAIN THE PLT WAS QUESTIONED, BUT HE ELECTED TO CONTINUE THE APPRCH. THE PLT WAS ADVISED BY THE CONTROLLER AS THE OM WAS PASSED. THE PLT ACKNOWLEGD AND THERE WAS NO DISTRESS CALL. THE ACFT WAS OBSERVED BY GROUND WITNESSES BELOW THE OVERCAST SKIES PRIOR TO CRASHING 1.1 MILES INSIDE THE OM. THE ACFT COLLIDED WITH TRESS, WIRES AND A RESIDENCE. THE ACFT & RESIDENCE WERE DESTROYED BY THE IMPACT & FIRE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC84FA163
- Event ID
- 20001214X39710
- Case number
- NYC84FA163
- 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 1984-05-08.
- API snapshot SHA-256: 8238995b5b099615cafbc9c831695e17b081ed442de53001ae1d954a8e32cc7f; retrieved 2026-09-21T05:32:47.672Z.