FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17LA285 · Hillard Charlie R HAWKER FB60

25 Jul 2017 · Breckenridge, TX, United States

Hillard Charlie R HAWKER FB60 · Accident: loss of engine power (total) on approach

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

Report a problem

Event

NTSB case
CEN17LA285
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

Hillard Charlie R HAWKER FB60

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
N254SF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stephens County Airport (BKD), Breckenridge, TXTo Stephens County Airport (BKD), Breckenridge, TX
Aircraft age
About 61 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
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
Loss of engine power (total)
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

  • Not determined › Not determined

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

NTSB narrative

A witness, who was a repair facility employee, stated that, on the morning of the accident, the airplane was fueled and then flown for about 15 to 20 minutes without incident. The accident flight was the second flight of the day and was also about 15 to 20 minutes long. The witness's cell phone video revealed that the airplane was on short final for the runway as it descended and turned left; it then disappeared into a wooded area. The airplane collided with a tree and then impacted the ground and came to rest upright. First responders to the accident site stated that the fuel lines had been severed, and fuel was covering the ground under the airplane.

The propeller blades did not exhibit signs of power during impact. Postaccident testing of the engine's distributors and fuel pump did not reveal any anomalies. However, postaccident testing of the injection carburetor revealed that the right float switch pin was dislodged from its cylinder, but it could not be determined when the pin became dislodged. The pin was reinstalled into its cylinder, and subsequent testing of the injection carburetor revealed that it was out of tolerance; however, the specialists at the repair station stated that, although several of the carburetor readings were out of tolerance, none of the indications would have caused a loss of engine power.

Postaccident examination of the engine did not reveal any evidence of preimpact mechanical malfunctions or anomalies that would have precluded normal operation. The fuel selector was found positioned to the auxiliary fuel tank line, not the main fuel tank line. The valve was impact-separated from the airplane, and its preaccident position could not be confirmed. Based on the available evidence, the reason for the loss of engine power could not be determined.

Probable cause

A total loss of engine power for reasons that could not be determined because postaccident engine examination and testing did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA285
Event ID
20170726X01812
Case number
CEN17LA285
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: 04352f168a9fedc68f72de3f69a4669fda7818b49ea042c20a2110d57461c1f7; retrieved 2026-09-16T05:36:33.585Z.