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

Quad City CHALLENGER accident near Wurtsboro, New York, June 5, 2020

On June 5, 2020 at about 11:25 pm local time, a 2012 Quad City CHALLENGER, an amateur-built aircraft,, registered N850RW, was substantially damaged in an accident during initial climb near Wurtsboro, New York (Wurtsboro-Sullivan County airport). It was a flight test under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of control after takeoff due to the pilot’s improper use of ballast weight. Contributing was the pilot’s decision to operate the airplane above its maximum gross weight.

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

What the record shows

Date
June 5, 2020 · about 11:25 pm local time
Place
Wurtsboro, New York · Wurtsboro-Sullivan County · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Quad City CHALLENGER II, built 2012, amateur-built
Registration
N850RW · no longer on the register · serial CH2-0905-2669
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

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

According to a witness, the airplane was tail heavy, so the pilot/owner and student pilot had added ballast to the front of the airplane and performed several high-speed taxi runs before departing for a test flight. After liftoff, the airplane began to yaw left and continued a left turn. The airplane did not climb and remained just above the treetops. The witness further reported that it sounded as though the pilot reduced engine power just before he lost sight of the airplane over the trees then heard the impact. The damage to trees and to the airplane was consistent with a low-energy impact. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. There were three canvas bags of sand ballast located in the forward section of the airplane that, when full, would have weighed about 22 lbs each. One of the ballast bags was wrapped around the bottom of the left rudder pedal and significantly torn, with about 5 lbs of sand remaining in the bag. There was a small amount of sand nearby, but not enough to total 22 lbs. The heavily torn ballast bag wrapped around the left rudder pedal and lack of residual sand nearby suggested that the base of the left rudder pedal likely got stuck on the left ballast bag at some point during the short flight, interfering with the flight controls and resulting in the left yaw and turn. The sand that escaped the torn left bag was likely scattered during the impact sequence, leaving very little sand near the left ballast bag when the airplane came to rest. Weight and balance calculations revealed that the airplane was 127 lbs over the maximum gross weight of 800 lbs, of which about 66 lbs was ballast. Given this information, it is likely that the pilot’s improper use of ballast weight resulted in further exceedance of the airplane’s maximum gross weight and that the placement of the ballast resulted in an interference with the rudder controls. It is likely that these two factors limited the airplane’s controllability and ability to climb, and directly contributed to the loss of control during takeoff and subsequent impact with terrain.

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. Loss of control in flight during initial climb defining event
  2. Aircraft loading event during prior to flight

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Yaw control › Attain/maintain not possible
  • Aircraft › Aircraft oper/perf/capability › Aircraft capability › Maximum weight › Capability exceeded
  • Aircraft › Aircraft handling/service › Loading › (general) › Incorrect use/operation
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot

Pilot

  • Certificate: sport pilot
  • Flight time: 14.8 hours in all
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: unk
  • Injury: fatal

Pilot-Rated Passenger

  • Certificate: student
  • Flight time: 183 hours in all
  • Medical certificate: Class 3
  • Seat: unk
  • Injury: fatal

The aircraft

  • Airframe total time: 14 hours
  • Last inspection: condition inspection, September 5, 2019
  • Maximum gross weight: 800 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 503UL (piston); 0 hours total

The flight

  • Departed from: N82 Wurtsboro NY at 11:23 pm
  • Flight plan: none
  • Runway 23, 3,591 ft by 60 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 230° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 66°F (19°C)
  • Altimeter: 29.82 inHg
  • Observation at 10:54 pm from MGJ, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew2

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

13 documents, released by the NTSB on June 10, 2022. 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.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.