ERA15FA175 · Bedecorp LLC BD-22
Bedecorp LLC BD-22 · Accident: abrupt maneuver on approach
From Treasure Coast International Airport (FPR) to Treasure Coast International Airport (FPR)
Event
- NTSB case
- ERA15FA175
- 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
Bedecorp LLC BD-22
- Aircraft type
- Bedecorp BD-22
- 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
- N224BD
- Operator
- Bedecorp
- Onboard fatalities
- Unknown
- Route
- From Treasure Coast International Airport (FPR), Fort Pierce, FLTo Treasure Coast International Airport (FPR), Fort Pierce, FL
- Aircraft age
- About 1 year (built 2014)
- 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
- Abrupt maneuver
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot was tasked with performing high-speed taxi tests and familiarization with the experimental airplane. After performing two high-speed taxis, the pilot requested taxi clearance to the active runway, received a takeoff clearance, and departed from the runway. Witnesses reported that, after departure and while in the traffic pattern, the airplane's pitch oscillated and that, when it turned onto the final leg of the traffic pattern, it continued to pitch up and down. The airplane subsequently descended and impacted terrain about 1 mile from the approach end of the runway.
Images captured by an onboard video recorder provided information about where the pilot's attention was directed, his interaction with the flight controls, and the status of cockpit instruments and engine indicators. The information indicated that the pilot did not pin his left arm to the armrest and that he used his entire forearm to move the airplane's sidestick flight control. In addition, the pilot released and re-gripped the sidestick several times, which exacerbated the negative g maneuvers. These control inputs were indicative of the pilot overcontrolling the airplane. As the pilot flew the right-hand traffic pattern, he repeatedly turned his head right and/or reached right. These movements and distractions resulted in the airplane beginning to oscillate. In each of the pitch excursions, except for one that occurred during the takeoff, the pilot's left arm moved fore and aft, and negative gs were present. During the flight, as the speed increased, each pitch oscillation increased; the final adjustment of the flight control by the pilot resulted in an overstress of the airframe and its subsequent in-flight breakup.
A postaccident examination of the airframe, flight controls, and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Although the pilot reported a high level of total flight experience, he had accumulated less than 1/2 hour of total flight experience in the accident airplane make and model at the time of the accident. The airplane manufacturer's flight test policy indicated that, to gain experience, pilots should first taxi the airplane, then perform high-speed taxis, then perform high-speed taxis with the nose gear off the ground, and finally, after the pilot was comfortable with the airplane, to perform a takeoff. The pilot decided to perform the takeoff without the requisite experience; therefore, he was operating contrary to the manufacturer's flight test policy.
Probable cause
The pilot's excessive pitch control inputs to the airplane’s sidestick control, which resulted in an overstress of the airframe and its subsequent in-flight breakup. Contributing to the accident was the pilot's decision to operate the airplane contrary to the manufacturer's flight test policy.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15FA175
- Event ID
- 20150401X15516
- Case number
- ERA15FA175
- 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: 29ec7d6d9b77eaed3eba845e3a1a54bdd1f19e1711bff22435bc4d19c3541588; retrieved 2026-09-14T17:34:15.099Z.