Temsco Helicopters Hughes 369D accident
Hughes 369D · Accident: in flight collision with object during initial climb
Event
- NTSB case
- SEA89LA170
- 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
- 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
Hughes 369D
- Aircraft type
- Hughes 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
- N1088N
- Operator
- Temsco Helicopters
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 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
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Clearance, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER PICKING UP PASSENGERS WITH EQUIPMENT, THE PILOT ATTEMPTED TWICE TO LIFT OFF, BUT WAS UNSUCCESSFUL. ON THE THIRD ATTEMPT, THE HELICOPTER ATTAINED AN ALTITUDE OF APRX 20 FT; HOWEVER, IT DID NOT CLEAR A LINE OF TREES LOCATED 50 FT FROM THE LIFT-OFF POINT AND 30 FEET IN HEIGHT. AFTER THE ACCIDENT, THE PASSENGERS AND EQUIPMENT WERE WEIGHED. THE HELICOPTER WAS FOUND TO HAVE BEEN OPERATING 200 POUNDS OVER ITS MAX GROSS WEIGHT LIMITATION. THERE WERE NO REPORTED MECHANICAL FAILURES OR MALFUNCTIONS.
Probable cause
THE PILOT FAILED TO OBTAIN CLEARANCE OVER TREES. CONTRIBUTING TO THE ACCIDENT WAS: THE AIRCRAFT BEING ABOVE ITS MAXIMUM CERTIFICATED GROSS WEIGHT LIMITATION AND THE TREES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA89LA170
- Event ID
- 20001213X29499
- Case number
- SEA89LA170
- 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: 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-09-09.
- API snapshot SHA-256: 19b07db11f420033754e6e61b523f9f507f48cbfc9789d75308b72a4a7407f0a; retrieved 2026-09-18T19:08:31.216Z.