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

Amateur-built CHALLENGER accident near Plant City, Florida, June 9, 2012

On June 9, 2012 at about 3:26 pm local time, a amateur-built CHALLENGER, registered N2571T, was substantially damaged in an accident during approach (VFR pattern final) near Plant City, Florida (Blackwater Creek Ultralight Fl airport). It was a personal flight 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 non-certificated pilot’s loss of control during approach and landing. Contributing to the accident was the pilot’s lack of both total and recent flight experience.

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

What the record shows

Date
June 9, 2012 · about 3:26 pm local time · cases in 2012
Place
Plant City, Florida · Blackwater Creek Ultralight Fl · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built CHALLENGER
Registration
N2571T · no longer on the register · serial CH20970
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

According to the airport manager, the purpose of the flight was for the pilot/owner to get “one last flight” in the airplane before he sold it. The pilot had experienced health issues and undergone surgery in the years prior to the accident, and had not flown the airplane in about 1 year. The manager watched the entire flight and described the takeoff as “normal.” The first landing approach was “fast and long,” and the pilot performed a go-around and entered the traffic pattern for a second approach. The manager and other witnesses stated that the airplane descended on the base leg of the traffic pattern to about 500 feet, and that the airplane turned and aligned with the runway. During the descent on final approach, the airplane pitched up, leveled off, descended, and pitched up multiple times with corresponding changes in engine power. The airplane “wandered” to the west and was briefly flying parallel to the runway as it headed toward the witnesses on the grass apron and the hangars on the west side of the field. The airplane then pitched up, the nose dropped, and the airplane impacted the ground in a nose-down attitude of about 25-30 degrees. During the descent and at ground contact, the engine was running “at cruise power,” according to the airport manager. The engine continued to run after the accident, and first responders had to pull one of the carburetors from its mount in order to stop the engine. The 79 year-old pilot/owner had never obtained a pilot certificate. Over the 60 years that he documented his flight time, the pilot reported 122 total flight hours. The accident airplane was purchased almost 20 years before the accident but was not registered until 5 years before the accident. At the time of the accident, the airplane had accumulated 19 total airframe hours.

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 approach (VFR pattern final) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Recent experience › Pilot
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience › Pilot

Pilot

  • Certificate: student
  • Flight time: 122 hours in all; 20 in this make and model
  • Medical certificate: None
  • Seat: frt
  • Injury: fatal

The aircraft

  • Airframe total time: 19 hours
  • Last inspection: condition inspection, June 5, 2012; 0 hours since
  • Maximum gross weight: 1,120 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 503 (piston); 0 hours total

The flight

  • Departed from: 9FD2 Plant City FL at 3:15 pm
  • Destination: 9FD2 Plant City FL
  • Flight plan: none
  • Runway 36, 2,300 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 160° at 3 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,000 ft
  • Temperature: 86°F (30°C), dew point 75°F (24°C)
  • Altimeter: 30.02 inHg
  • Observation at 3:15 pm from KPCM, 8 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

9 documents, released by the NTSB on February 11, 2013. 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.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA12FA387.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.