FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC83FA207 · Cessna 310Q

12 Aug 1983 · Scranton, PA, United States

Cessna 310Q · Accident: partial loss of engine power (mechanical failure) en route

From Wilkes-Barre/Scranton International Airport (AVP) to Lehigh Valley International Airport (ABE)

Report a problem

Event

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

Cessna 310Q

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
N69JM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wilkes-Barre/Scranton International Airport (AVP)To Lehigh Valley International Airport (ABE), Allentown, 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
En route · climb to 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
Partial loss of engine power (mechanical failure)
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

  • Ignition system, magneto › Failure, total
  • Ignition system, magneto › Improper
  • Ignition system, magneto › Shorted
  • Other maintenance personnel › Maintenance, improper
  • Pilot in command › Aircraft handling, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

SHORTLY AFTER TAKEOFF THE ACFT WS OBSERVED ON RADAR MAKING A LEFT 360 DEG TURN. THE PLT DID NOT RESPOND TO A CALL FROM THE CONTROLLER. A WITNESS HEARD THE PLANE 'SPUTTERING' & OBSERVED IT IN ERRATIC MANEUVERS PRIOR TO IT HITTING A HOUSE. POST EXAM REVEALED THAT THE LEFT ENG'S LEFT MAGNETO DID NOT PRODUCE ANY SPARK DURING IT'S FUNCTIONAL CHECK. UPON DIS- ASSEMBLY THE CONDENSER WIRE SHIELDING WAS FOUND PARTIALLY CUT & HAD SHORTED ON THE MAGNETO DRIVE. THIS WAS DETERMINED TOHAVE BEEN THE RESULT OF IMPROPER ROUTING THAT EXPOSED THE WIRE TO THE MAGNETO DRIVE. THE ACFT & ENGS HAD AN ANNUAL INSPECTION COMPLETED 8/10/83.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC83FA207
Event ID
20001214X44304
Case number
NYC83FA207
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: 76e8a386992a42bd9def68e2ef50a47930e4cfc4a5d538a94a4ff6d173bfb20d; retrieved 2026-09-21T06:21:07.901Z.