FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA143 · Hawker SEA FURY ISS 25

18 Feb 2014 · Breckenridge, TX, United States

Hawker SEA FURY ISS 25 · Accident: powerplant system/component malfunction/failure during initial climb

From Stephens County Airport (BKD) to Stephens County Airport (BKD)

Report a problem

Event

NTSB case
CEN14FA143
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
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 SEA FURY ISS 25

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
N13HP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stephens County Airport (BKD), Breckenridge, TXTo Stephens County Airport (BKD), Breckenridge, TX
Aircraft age
About 58 years (built 1956)
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
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
Powerplant system/component malfunction/failure
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
  • Aircraft › Aircraft propeller/rotor
  • Not determined › Not determined
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After several hours of ground instruction and one solo flight, the private pilot was making only his second takeoff in a single-seat Hawker Sea Fury airplane. Two witnesses standing at midfield reported hearing abnormal engine and propeller sounds during takeoff, and the airplane's speed seemed to be slower than normal. Another witness, who had pilot experience in the Hawker Sea Fury, did not see the takeoff but reported that he could clearly hear the engine "screaming," and he knew at that moment that the accident pilot was experiencing a propeller overspeed.

A flight instructor was conducting a formation takeoff in trail behind the accident airplane to observe the flight. After his takeoff, he joined in on the right side of the accident airplane and he heard the accident pilot make a radio transmission that he had an overspeed and the airplane's rpm was at 3,500. The instructor reported that the maximum takeoff power was about 2,900 rpm. No further transmissions from the accident pilot were heard. The instructor kept repeating for the pilot to pull the power back and keep the nose down. Both airplanes climbed to about 1,000 ft above ground level, and the accident airplane began a slow turn to the left. The flight instructor continued to fly in formation with the accident airplane and continued to transmit instructions to the accident pilot to lower the nose and reduce the throttle. However, the accident airplane continued to slow and fly in a nose-up attitude until it stalled and rolled to the right. It then entered a vertical nose-down dive and impacted terrain. The flight instructor and witnesses reported that there was an immediate explosion and postimpact fire.

The witnesses' description of abnormal engine and propeller sounds and the accident pilot's report of 3,500 rpm are indicative of a runaway propeller. The Hawker Sea Fury emergency checklist indicated that recovery from a runaway propeller was possible when following the procedures listed in the checklist, which include reducing the throttle, decreasing the propeller angle, and maintaining an airspeed of 140 knots.

A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. A laboratory examination of the impact- and thermally damaged propeller regulator did not show any obvious evidence of preimpact mechanical malfunction or abnormalities. The cause of the runaway propeller could not be undetermined.

Probable cause

The pilot’s inadequate emergency response to a runaway propeller and his failure to maintain airspeed, which resulted in the airplane exceeding its critical angle-of-attack and stalling. The cause of the runaway propeller was undetermined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA143
Event ID
20140218X21224
Case number
CEN14FA143
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: 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: 93c302e337b9983e60837f60f4b5b53278cf58b78bc63f2133c20cd8d82dd6ec; retrieved 2026-09-14T16:10:47.419Z.