Amateur-built Kitfox accident near Indian Trail, North Carolina, March 3, 2011
On March 3, 2011 at about 9:00 pm local time, a amateur-built Kitfox, registered N788Q, was substantially damaged in an accident during takeoff near Indian Trail, North Carolina (Goose Creek airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain directional control during an aborted landing, resulting in a runway excursion and collision with a vehicle.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 3, 2011 · about 9:00 pm local time
- Place
- Indian Trail, North Carolina · Goose Creek · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built Kitfox 4-1200
- Registration
- N788Q · no longer on the register · serial 1893
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that the airplane bounced several times during the landing. After the third bounce, he elected to abort the landing and applied full engine power. The airplane veered to the left, departed the left side of the runway and struck an unoccupied parked vehicle before stopping. The airplane sustained substantial damage to the left wing and fuselage. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane.
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
- Abnormal runway contact during landing (flare/touchdown)
- Loss of control on ground during takeoff defining event
- Collision during takeoff/land during takeoff
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 463 hours in all; 12 in this make and model; 23 in the last 90 days; 12 in the last 30 days; 369 as pilot in command
- Last flight review: December 29, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 12 hours
- Last inspection: condition inspection, January 22, 2011
- Maximum gross weight: 1,200 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912UL (piston); 0 hours total
The flight
- Departed from: 28A Indian Trail NC at 8:30 pm
- Destination: 28A Indian Trail NC
- Flight plan: none
- Runway 04, 2,350 ft by 35 ft
Weather at the time
- Light: daylight
- Wind: at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 57°F (14°C), dew point 43°F (6°C)
- Altimeter: 30.40 inHg
- Observation at 8:53 pm from EQY, 6 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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.