ATL00LA030 · Burak Stanley A XF4
Burak Stanley A XF4 · Accident: partial loss of engine power (mechanical failure) en route
From Bailing Airport (BKV) to an unrecorded destination
Event
- NTSB case
- ATL00LA030
- 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
Burak Stanley A XF4
- Aircraft type
- Burak Stanley XF4
- 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
- N9VY
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bailing Airport (BKV)To not recorded
- 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
- 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
- Partial 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
- Owner/builder › Design stress limits of aircraft, exceeded
- Owner/builder › Material inadequate, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Approximately 35 minutes in to the flight, the pilot experienced a loss of propeller thrust. The pilot stated that he heard a loud 'bang' from the engine compartment and experienced loss of thrust. The pilot said that the engine tachometer went to redline, and the propeller rpm decreased. The pilot said , changing the engine rpm did not change the propeller rpm. The pilot declared an emergency and started an emergency descent for a landing on runway 27. As the pilot maneuvered the airplane on the final approach, he cleared a stand of trees on the final approach to runway 27. While on short final to land, the airplane initially collided with the ground short of the runway surface and subsequently came to rest on a taxiway. The examination of the wreckage revealed that the Rex Flex Coupling Assembly had failed and that three out of the six Rex Bolts had also failed. The pilot stated that the Flexidyne Drive Shaft was designed for a 100 horse-power engine. The pilot/builder stated that he installed a 150 horse power engine on the airplane.
Probable cause
The owner/builder's failure to build the airplane within the design stress limits of the drive shaft assembly, that resulted in the failure of the Flex Coupling Retention Bolts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL00LA030
- Event ID
- 20001212X20450
- Case number
- ATL00LA030
- 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: 7ac41b5673bcc8da82b48024c501ada1e283c778a4664911d92cba9b38db6c5c; retrieved 2026-09-21T20:17:59.541Z.