FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Newair Flight de Havilland DHC-6-100 incident

12 Feb 1982 · Jamaica, NY, United States

de Havilland DHC-6-100 · Incident: total loss of engine power (mechanical failure) en route

From Philadelphia International Airport (PHL) to John F. Kennedy International Airport (JFK)

Report a problem

Event

NTSB case
NYC82IA036
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
Incident
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
0 · 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
Charter & commuter
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

de Havilland DHC-6-100

Aircraft type
de Havilland DHC-6
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
N80701
Onboard fatalities
Unknown
Route
From Philadelphia International Airport (PHL), PHILADEPHIA, PATo John F. Kennedy International Airport (JFK), NEW YORK, NY
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 135: Air Taxi & Commuter
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 · 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
Total 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
None

Cause areas

  • Compressor assembly, blade › Fatigue

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

NTSB narrative

DURING CRUISE FLIGHT, THE AIRCRAFT EXPERIENCED A POWER FAILURE AND FIRE IN THE LEFT ENGINE. THE CREW SECURED THE ENGINE AND DISCHARGED THE FIRE EXTINGUISHER WITHOUT EFFECT ON THE FIRE. DURING DESCENT TO JFK INTERNATIONAL THE FIRE EXTINGUISHED ITSELF. A NORMAL SINGLE ENGINE LANDING WAS MADE AND THE PASSENGERS DEPLANED WITHOUT INJURY. INVESTIGATION REVEALED THAT A COMPRESSOR TURBINE BLADE HAD FAILED IN FATIGUE DAMAGING POWER TURBINE BLADES, THE POWER TURBINE VANE RING AND THE COMPRESSOR TURBINE VANE RING. IN ADDITION THE PROPELLER REDUCTION GEARBOX WAS DAMAGED. THE ORIGIN AND NATURE OF THE FATIGUE IN THE TURBINE BLADE WAS NOT DETERMINED. IT WAS DETERMINED THAT THE FAILED BLADE WAS INSTALLED AT OVERHAUL, ABOUT 843 HOURS BEFORE THE INCIDENT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC82IA036
Event ID
20020917X02571
Case number
NYC82IA036
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, damage. 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: f378b86449c8713fa158bcf298b1c319041ad63ad61cbd94c022129e7285ab4b; retrieved 2026-09-18T21:12:28.630Z.