FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05TA156 · Sikorsky S-70A

4 May 2005 · Calabasas, CA, United States

Sikorsky S-70A · Accident en route

From Pacoima, CA to Malibu, CA

Report a problem

Event

NTSB case
LAX05TA156
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
0 · all aircraft and ground
Ground fatalities
Unknown
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
Government
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

Sikorsky S-70A

Aircraft type
Sikorsky S-70
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
N160LA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pacoima, CATo Malibu, CA
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
Public Aircraft
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
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Door, inspection › Separation
  • Manufacturer › Material inadequate, improper
  • Miscellaneous, bolt/nut/fastener/clamp/spring › Fatigue

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The left auxiliary power unit (APU) door departed the helicopter in flight and contacted the main rotor blades. The pilot made precautionary landing. The APU door is located on the top of the helicopter, near the main rotor blades, and it is secured using two upper and lower, push-pin type snap latches. Following the accident, the latches were located separately in a field; each latch remained secured to portions of the door material. The APU door is opened and secured by maintenance daily and its security was verified by the pilot during the preflight. Post accident examination of the two fractured sections of left APU door with latches and the two hinge keepers showed that the hinge keepers failed as a result of fatigue fractures and allowed the door to separate in flight. Review of the manufacturer's process specifications disclosed that the failed hinge keepers were manufactured by a now superceded production process. This superceded production process introduced contamination, which resulted in fatigue of the hinge keepers. A new hinge was designed and implemented over 2 years prior to the accident; however, there was no recall by the helicopter manufacturer to replace the older design. In the United States, two civilian operators use this helicopter (five helicopters total) and the primary operator is the United States military. The United States military has classified this as a low-risk issue. Due to the damage sustained to the parts, the manufacturer was unable to confirm that the problem would have been detectable by flight crew or maintenance personnel prior to the accident flight using the current inspection methods.

Probable cause

fatigue of the forward keeper due to known flaws in the manufacturing process.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05TA156
Event ID
20050507X00571
Case number
LAX05TA156
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, coordinates. 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: 0f920fef5083eb9b0a83ff4d9497f869f1e8ea16ac32ee2f7e84c1c5c35fc189; retrieved 2026-09-18T21:16:05.232Z.