FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL92FA029 · Aerospatiale AS350D ASTAR AS350D AST

7 Dec 1991 · Fuquay-Varina, NC, United States

Equipment Leasors of Pa Aerospatiale AS350D ASTAR AS350D AST · Accident: total loss of engine power (mechanical failure) en route

From Wilmington, NC (no airport) to Durham, NC (no airport)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
ATL92FA029
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
3 · 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

Aerospatiale AS350D ASTAR AS350D AST

Aircraft type
Aerospatiale AS350
Category
Helicopter
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
N26FH
Onboard fatalities
Unknown
Route
From Wilmington, NC (no airport)To Durham, NC (no airport)
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 · 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
Destroyed

Cause areas

  • Engine assembly, bearing › Seized
  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › Operation with known deficiencies in equipment, continued

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

NTSB narrative

THE NEWS HELICOPTER WAS RETURNING FROM A REPORTING ASSIGNMENT AT NIGHT IN VMC CONDITIONS. THE SOLE SURVIVOR, A SPORTSCASTER, REPORTED THAT ABOUT 20 TO 25 MINUTES BEFORE THE CRASH, THE ENGINE CHIP LIGHT CAME ON. THE LIGHT CAME ON AND WAS RESET BY THE PILOT 5 TO 10 TIMES. THERE WAS ALSO A LOSS OF TORQUE ON THE TORQUE GAUGE. SUBSEQUENTLY, THE ENGINE LOST POWER & THE HELICOPTER CRASH LANDED IN AN OPEN FIELD. AN INSPECTION OF THE ENGINE REVEALED THE #2 BEARING HAD SEIZED, RESULTING IN FAILURE OF THE COMPRESSOR SHAFT. THE #2 BEARING HAD BEEN REPLACED DURING RECENT ENGINE MAINTENANCE, AND THERE WAS ONLY ABOUT 125 HOURS ON THE NEW BEARING. THE OIL JET TO THE BEARING WAS NOT BLOCKED OR CLOGGED. THERE WERE TORQUE FLUCTUATIONS OBSERVED ON TWO OCCASIONS DURING THE WEEK BEFORE TO THE ACCIDENT. SEVERAL COMPONENTS WERE CHANGED IN AN ATTEMPT TO PINPOINT THE PROBLEM. THE SURVIVOR'S SEAT BELT FAILED IN THE CRASH DUE TO AN IMPROPER INSTALLATION, AND HE WAS THROWN CLEAR OF THE WRECKAGE.

Probable cause

THE PILOT'S IMPROPER DECISION IN CONTINUING THE FLIGHT WITH A KNOWN ENGINE PROBLEM, AND THE SUBSEQUENT SEIZURE OF THE NUMBER TWO ENGINE BEARING, RESULTING IN ENGINE STOPPAGE. DARKNESS WAS A RELATED FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL92FA029
Event ID
20001212X18539
Case number
ATL92FA029
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: dd73cf914268eed9a53244d2439a0e2684b9f630fa3378ccd913526d48c9d50e; retrieved 2026-09-21T01:27:39.679Z.