LAX02FA281 · Aerospatiale AS350BA
Aerospatiale AS350BA · Accident: airframe, component or system failure en route
From Harry Reid International Airport (LAS) to Harry Reid International Airport (LAS)
Event
- NTSB case
- LAX02FA281
- 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
- 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 AS350BA
- 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
- N357NT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Harry Reid International Airport (LAS), Las Vegas, NVTo Harry Reid International Airport (LAS), Las Vegas, NV
- 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
- Substantial
Cause areas
- Pilot in command › Airspeed, not maintained
- Pilot in command › Directional control, not maintained
- Pilot in command › Emergency procedure, not followed
- Pilot in command › Rotor RPM, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter landed hard following a loss of directional control during a precautionary landing after a hydraulic system failure, with the main rotor blades cutting off the tail boom. This was a tour flight that was en route back to the departure airport when a complete hydraulic system failure occurred and the pilot decided to make a precautionary landing at a nearby airport. He had planned on conducting a run-on landing; however, during the approach the airspeed dropped to 30 knots. The helicopter's nose dropped and it started to spin to the left. The pilot pulled back on the cyclic enough to get the nose up; however, forward airspeed continued to decay and the rotation rate increased. The pilot said that the flight controls were not responding, and he believed the only way to stop or slow the rotation was to shutdown the engine. The helicopter completed two revolutions before it impacted the ground in a nose level attitude, 180 degrees from its original direction of travel. A witness to the accident reported the altitude of the helicopter as it began to spin was about 30-50 feet above the ground and he saw the main rotor blades cone upward as it fell to the ground. For a hydraulics failure, Federal Aviation Administration approved flight manual required the pilot to reduce the collective pitch and adjust the airspeed between 40 to 60 knots in level flight. The pilot was then instructed to cut off the hydraulic pressure by activating the collective lever pushbutton, and to make a flat approach over a clear landing area and land with forward speed. During examination of the hydraulic pump, investigators noted that the coupling sleeve splines were worn beyond serviceable limits. They also noted the general condition as rust colored, and no lubrication was found inside the pump housing or coupling sleeve splines. A company maintenance work order contained a serviceable tag for the hydraulic pump assembly. The serviceable tag that the operator's maintenance personnel wrote said that the hydraulic pump was "inspected, cleaned filter, new O rings installed on connections, inspected coupling, new pump assembled." The maintenance records also revealed that the assembled hydraulic pump was installed 15 days prior to the accident and had been in service for 74.6 hours when it failed. A metallurgical examination of the hydraulic pump revealed that it had failed due to the wearing away of the splines on the coupling sleeves. The wear was due to insufficient lubrication and soft splines on both coupling sleeves. The failure mode was assisted by an increase in internal rotational resistance at operating temperatures. The hardness testing indicated that the case hardened layer on the splines was not deep enough and the hardness, within the layer, was slightly below the specified range. The inner surfaces of the gear bearings displayed rubbed areas, consistent with hard contact, and areas of bluing, consistent with elevated temperatures. Examination of the coupling sleeves revealed a total loss of inwardly protruding spline material and hardness below the design requirements. The manufacturer's maintenance manual requires that the pump drive shaft, coupling sleeves, and bearing be packed with "abundant" grease during assembly. The examination found only a trace amount of grease in the coupling sleeves that did not satisfy the "abundant" requirement specified in the manufacturer's maintenance manual. There was rust on the front retaining rings and bearings, which indicated that there was insufficient grease in the splines to retain it or lubricate the splines.
Probable cause
the pilot's failure to maintain an adequate airspeed and main rotor rpm during the landing approach as prescribed in the hydraulic pump failure emergency procedures found in the rotorcraft flight manual, thus resulting in a loss of control of the aircraft and the subsequent crash. Contributing to the accident was the failure of the hydraulic pump due to excessive coupling spline wear which was caused by the application of insufficient lubrication by the operator's maintenance personnel during pump installation and the improper manufacturing of the couple sleeve.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02FA281
- Event ID
- 20020926X05225
- Case number
- LAX02FA281
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2002-09-12.
- API snapshot SHA-256: 669443c135975358cb8b79eb9ce005a7e64e6a49f197cdf3d6a04d568125c00c; retrieved 2026-09-18T15:58:13.560Z.