LAX90FA060 · McDonnell Douglas 369E
Interwest McDonnell Douglas 369E · Accident: loss of control in flight during initial climb
From Charles M. Schulz Sonoma County Airport (STS) to an unrecorded destination
Event
- NTSB case
- LAX90FA060
- 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
McDonnell Douglas 369E
- Aircraft type
- McDonnell Douglas 369
- 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
- N1604L
- Operator
- Interwest
- Onboard fatalities
- Unknown
- Route
- From Charles M. Schulz Sonoma County Airport (STS)To not recorded
- 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
- Initial climb
- 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
- Loss of control in flight
- 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
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT EXECUTED AN IMMEDIATE LEFT DOWNWIND CLIMBING TURN WHEN HE DEPARTED THE HELIPAD AND EXPERIENCED A LOSS OF TAIL ROTOR EFFECTIVENESS. BEFORE DEPARTING, THE PILOT FAILED TO ACCOUNT FOR THE DOWNWIND TURN AND THE HELICOPTER'S EXCEEDING THE MAXIMUM GROSS WEIGHT. THE POST ACCIDENT INVESTIGATION DISCLOSED THE LATERAL TRIM MOTOR EXCEEDED ITS PHYSICAL EXTENSION LIMITS WHICH INDICATES THAT THE TRIM MOTOR WAS OPERATING DURING THE IMPACT SEQUENCE WHEN ITS AIRFRAME ATTACHMENT POINT WAS BROKEN.
Probable cause
THE PILOT'S IMPROPER PREFLIGHT PLANNING/DECISION WHICH RESULTED IN THE LOSS OF TAIL ROTOR EFFECTIVENESS. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT ALLOWING THE MAXIMUM GROSS WEIGHT OF THE AIRCRAFT TO BE EXCEEDED, AND THE TAILWIND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90FA060
- Event ID
- 20001213X29968
- Case number
- LAX90FA060
- 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: 5b27e66afa5bd1c96b609c2a3bf74efb9325bc1dfd15771bff44386ac9565db1; retrieved 2026-09-21T03:03:00.432Z.