NYC83FA054 · Cessna 310R
Cessna 310R · Accident: in flight collision with object on approach
From Dupage Airport (DPA) to an unrecorded destination
Event
- NTSB case
- NYC83FA054
- 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
- 4 · 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
Cessna 310R
- 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
- N310TA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dupage Airport (DPA), DU PAGE, ILTo 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
- Approach · IFR missed 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, below
- Pilot in command › Missed approach, delayed
- Pilot in command › Proper climb rate, not attained
Approximate · Estimated position: the centre of Atlantic City, NJ, the place the record names. Not the accident site.
NTSB narrative
THE FLT PROCEEDED ROUTINELY FROM CHICAGO TO ATLANTIC CITY. COMMUNICATIONS AND PROCEDURES ALL SEEMED ROUTINE AND NORMAL AND AT 1901 LOCAL CONTROL AT ATLANTIC CITY INFORMED THE PILOT THAT HE WAS ONE MILE OUT AND SHOULD BE PICKING UP THE 'RABBIT' MOMENTARILY. AT 1902 THE CONTROLLER ASKED THE PILOT IF HE WAS ON THE GROUND OR DID HE GO AROUND? THE PILOT RESPONDED THAT HE WAS 'IN THE GO-AROUND.' LOCAL CONTROL THEN ISSUED MISSED APPROACH PROCEDURES. THE FLT DID NOT RESPOND TO THE INSTRUCTIONS NOR TO ANY SUBSEQUENT TRANSMISSIONS. AT 1907 AN EXPLOSION WAS REPORTED IN THE VICINITY OF THE GARDEN STATE PARKWAY. THE ACFT STRUCK TREES 5,900 FT BEYOND THE DEPARTURE OF THE 10,000 FT RWY ON A TRACK OF 110 DEG. THE TREES IN THE AREA WERE ABOUT 45 FT HIGH.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA054
- Event ID
- 20001214X42074
- Case number
- NYC83FA054
- 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 1983-01-29.
- API snapshot SHA-256: 4b1aa1e4971ff0fae0afeb558b919809c2a9fe3df8c380056150cc3bfb030ba2; retrieved 2026-09-21T07:14:26.411Z.