LAX00LA034 · Hawker Siddeley HUNTER T MK 7 HUNTER T M
Advanced Training Systems Int Hawker Siddeley HUNTER T MK 7 HUNTER T M · Accident: total loss of engine power (mechanical failure) during initial climb
From Ivanovo South Airport (IWA) to Point Mugu Naval Air Station (Naval Base Ventura Co) (NTD)
Event
- NTSB case
- LAX00LA034
- 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
- 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
Hawker Siddeley HUNTER T MK 7 HUNTER T M
- Aircraft type
- Hawker Siddeley HUNTER T MK 7
- Category
- Airplane
- 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
- N576NL
- Operator
- Advanced Training Systems Int
- Onboard fatalities
- Unknown
- Route
- From Ivanovo South Airport (IWA)To Point Mugu Naval Air Station (Naval Base Ventura Co) (NTD), NAS POINT MUGU, 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
- 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
- Total loss of engine power (mechanical 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
- Compressor assembly, blade › Corroded
- Compressor assembly, blade › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Following a loss of engine power on the ex-British military jet fighter just after liftoff, the pilot aborted the takeoff on the runway but could not stop prior to over-running the departure end and colliding with a fence and a berm. The pilot and crew chief said that about 5-10 seconds after takeoff a significant compressor stall happened with a loud explosion, followed by engine spool down. The airplane is a two-seat ex-military jet fighter produced in the 1950's and early 1960's by Hawker for service in the British Royal Air Force. Following the airplane's surplus from the RAF, it was imported into the United States and was being flown under a FAA special airworthiness certificate in the experimental category for the purpose of exhibition and racing. According to records at Rolls-Royce, the engine was manufactured in 1954 and sent to the RAF as part of a spares contract. The engine was last in the factory overhaul facility on March 26, 1981, for overhaul at 251 hours TSO. The engine is life limited to 450 hours between overhauls. The last manufacturer's records on this engine documented its installation in another Hawker Hunter by the RAF in 1983, with 392 hours TSO. The operator's engine maintenance records began on June 27, 1990, and documented its installation in the accident airframe at a maintenance facility in Wisconsin. An unsigned handwritten note preceded this entry and stated that the engine had a total run time since overhaul of 436 hours, with 265 hours remaining to overhaul. No documentation was available to support the engine history between leaving RAF service and the installation in the accident airframe. The last entry in the records was dated July 2, 1999, and consisted of an annual inspection at a time of 548 hours since last overhaul. A partial engine disassembly revealed that three third stage compressor blades had fractured from their root fixing lugs and separated. All compressor blades from stages 5 through 10 had fractured through their airfoil sections just outboard of the root. The root lugs from the failed third stage were removed and submitted for metallurgical analysis. All three blades failed due to high cycle fatigue failures, which initiated in the bores of the lug fixing pins. Energy Dispersive X-ray revealed corrosion cracks and pits at the crack initiation site. This engine has a history of high cycle fatigue failures of stage 3 compressor blades due to corrosion pits. Two modifications were introduced by the manufacturer, which incorporated a strengthened lug and a silicon rubber sealant to the bore interface to prevent the corrosion induced fatigue failures. The modifications were performed by the RAF between 1983 and 1986 to in-service and spares stock engines. This engine did not have these modifications incorporated.
Probable cause
The fatigue failure and separation the stage 3 compressor blades due to corrosion pitting of the blade retention lug bores. A factor in the accident was the failure of the various post military surplus operators of this engine to incorporate the manufacturer's recommended modifications to prevent such failures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00LA034
- Event ID
- 20001212X20120
- Case number
- LAX00LA034
- 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: 0df933d260f9791819fd772a4cfd3395b298b9606d9728739787d59137bfce86; retrieved 2026-09-21T10:47:15.939Z.