The U.S. aircraft register, updated daily
Accidents · NTSB ERA15FA175 · Final report

Bedecorp LLC BD-22 accident near Fort Pierce, Florida, April 1, 2015

On April 1, 2015 at about 3:00 pm local time, a 2014 Bedecorp LLC BD-22, registered N224BD, was destroyed in an accident during approach (VFR pattern final) near Fort Pierce, Florida (St Lucie County Intl airport). It was a flight test under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 1, 2015 · about 3:00 pm local time · cases in 2015
Place
Fort Pierce, Florida · St Lucie County Intl · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Bedecorp LLC BD-22, built 2014
Registration
N224BD · no longer on the register · serial BD22-010
Damage
Destroyed
Flight
Flight test · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Abrupt maneuver during approach (VFR pattern final) defining event
  2. Loss of control in flight during approach (VFR pattern final)
  3. Collision with terrain or object (not controlled flight into terrain) during approach (VFR pattern final)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Dynamic load › Capability exceeded
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane single-engine; instrument: airplane
  • Flight time: 4,500 hours in all; 0.4 in this make and model
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1 hours
  • Last inspection: condition inspection
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming Engines O-235-L2C (piston); 672 hours total
  • Fire on the ground
  • Operator: Bedecorp LLC

The flight

  • Departed from: FPR Fort Pierce FL at 2:55 pm
  • Destination: FPR Fort Pierce FL
  • Flight plan: none
  • Runway 28L, 6,492 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 8 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 61°F (16°C)
  • Altimeter: 30.18 inHg
  • Observation at 2:53 pm from FPR, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

14 documents, released by the NTSB on July 6, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N224BD the same tail number, which may have belonged to a different aircraft at the time

2002-11-27LAX03LA040 · accident near Elko, NV · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ERA15FA175.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.