Heartflite Aerospatiale AS-350D accident
Aerospatiale AS-350D · Accident: airframe, component or system failure en route
From EASTPORT, ID to Holy Family Hospital Heliport (09WA)
Event
- NTSB case
- DEN89FA202
- 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
- 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
Aerospatiale AS-350D
- Aircraft type
- Aerospatiale AS-350
- 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
- N132SH
- Operator
- Heartflite
- Onboard fatalities
- Unknown
- Route
- From EASTPORT, IDTo Holy Family Hospital Heliport (09WA), Spokane, WA
- 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
- Airframe, component or system 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
- Rotorcraft flight control, swashplate assembly › Overtemperature
- Rotorcraft flight control, swashplate assembly › Seized
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE EMERG MED SVC (EMS/MEDEVAC) HELICOPTER WAS EN ROUTE WITH A PLT, 2 MED PSNL & A PATIENT. THE PATIENT (A FUGITIVE WITH A GUNSHOT WOUND) WAS HANDCUFFED TO THE STRETCHER. DRG FLT, THE PLT RPRTD A PROBLEM WITH THE PATIENT & REQUESTED POLICE ASSISTANCE DRG ARRIVAL AT THE HOSPITAL. THE PLT THEN TRANSMITTED AN EXPLETIVE & RADAR CONTACT WAS LOST WITH THE ACFT. WRECKAGE WAS FOUND OVER A 1 MI AREA WITH EVIDENCE OF AN IN-FLT BREAKUP & MAIN ROTOR CONTACT WITH THE COCKPIT & TAIL CONE. INV SHOWED EVIDENCE OF SWASHPLATE BRG SEIZURE. THE PITCH CHG LINK RODS & ROTATIONAL SCISSORS WERE BRKN IN THEDRCTN OF MAIN ROTOR ROTATION & CTC MARKS WERE FND ON THE FWD EARS OF THE ROTATING SWASHPLATE LUGS. DISASSEMBLY REVEALED FAILURE OF THE INNER & OUTER RACE LOCKS & SPALLING OF THE BRG RACES. LACK OF GREASE WAS NOTED IN THE BRG & THE BALL BRGSWERE DISCOLORED BLUE. WEAR MARKS ON THE BALL BRGS INDCD SCUFFING; 1 BALL BRG WAS FLUTED. THE BRG ASSEMBLY HAD ACCRUED 1.23 HRS OF OPN SINCE THE LAST 100 HR INSPN. LUBE REQUIRED EACH 400 HRS, COMPANY POLICY WAS TO LUBE AT 100 HR INTERVALS.
Probable cause
OVERHEATING AND SEIZURE OF THE SWASHPLATE BEARING, WHICH RESULTED IN AN INFLIGHT BREAKUP OF THE HELICOPTER AND SUBSEQUENT IMPACT WITH THE GROUND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN89FA202
- Event ID
- 20001213X29094
- Case number
- DEN89FA202
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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 1989-08-28.
- API snapshot SHA-256: 15d77a8e0f31349faa3d3dfd0123688af1476d80043281c09961a5b956dea40d; retrieved 2026-09-18T14:08:18.370Z.
- The NTSB's operator name is blank for N132SH; the operator shown is the name the NTSB records it doing business as.