WPR15GA030 · Hawker Aircraft Ltd HAWKER HUNTER MK.58
Hawker Aircraft Ltd HAWKER HUNTER MK.58 · Accident: aerodynamic stall/spin on approach
From Point Mugu Naval Air Station (Naval Base Ventura Co) (NTD) to Point Mugu Naval Air Station (Naval Base Ventura Co) (NTD)
Event
- NTSB case
- WPR15GA030
- 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
- 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
Hawker Aircraft Ltd HAWKER HUNTER MK.58
- Aircraft type
- Hawker HUNTER MK 58
- 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
- N332AX
- Operator
- Atac
- Onboard fatalities
- Unknown
- Route
- From Point Mugu Naval Air Station (Naval Base Ventura Co) (NTD), Oxnard, CATo Point Mugu Naval Air Station (Naval Base Ventura Co) (NTD), Oxnard, CA
- Aircraft age
- About 55 years (built 1959)
- 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
- Approach · VFR pattern final
- Defining eventThe 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
- Aerodynamic stall/spin
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was flying the single-seat turbojet airplane, which was owned and operated by a private company under contract to the United States Navy. The accident airplane was one of a flight of two airplanes that were returning to the airport to land at the conclusion of a training exercise. The accident airplane was to follow the lead airplane in an "overhead break" maneuver, which included overflying the runway, entering a descending, 270-degree turn to enter the downwind leg of the traffic pattern, then subsequently entering a descending, 180-degree turn to final approach. The recommended final approach airspeed was 150 knots (kts).
Witnesses observed both airplanes during the approach, and noted that the accident airplane's approach appeared lower and slower than that of the lead airplane. They stated that they observed the accident airplane in a left-wing-low bank, the wings rocked from side to side, then the airplane entered a rapid roll to the right and pitched down until it impacted the ground.
Recorded data recovered from the airplane's primary flight display unit revealed that the airplane crossed the runway's extended centerline about 5,900 ft from the runway threshold in a 30-degree bank at an airspeed about 126 kts. At this time, the airplane was on a magnetic heading about 25 degrees from runway alignment, at an altitude of about 328 ft; field elevation was 13 ft. Although the airspeed was well below the target airspeed, the airplane was on a heading, and in a geographic location, that permitted capture of the final approach path with bank corrections. Stall onset occurred several seconds later when the airplane was at a bank angle of 45 degrees, an airspeed of 114 kts, and an altitude of 276 ft. Data indicated that the pilot did not increase thrust significantly in the approach until at, or possibly about 1 second before, stall onset.
The stall was the result of the combination of an airspeed that was 46 knots below the minimum target value, and a bank angle that was significantly more than that required to capture the final approach path. Examination of the engine and flight controls did not reveal any mechanical deficiencies that would have adversely affected the performance or controllability of the airplane before impact.
The on-scene investigation revealed that the pilot did not attempt to eject from the airplane. Naval Air Systems Command simulations determined that a successful ejection could have been accomplished as late as 2 seconds before the end of the data (the data ended several seconds before impact).
Probable cause
The pilot's failure to maintain adequate airspeed during the approach for landing, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall/spin at an altitude too low for recovery.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15GA030
- Event ID
- 20141029X13346
- Case number
- WPR15GA030
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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 2014-10-30.
- API snapshot SHA-256: 4245ecbe6bbb93b7c56a3b53dea9db899d43b29786c00ca0e5cb689a1e882a80; retrieved 2026-09-14T17:28:16.603Z.