Aero Works Aero Lite 103 accident near Lincolnton, North Carolina, May 21, 2012
On May 21, 2012, a Aero Works Aero Lite 103 (ultralight), registered N2355L, was substantially damaged in an accident during initial climb near Lincolnton, North Carolina (Pvt Field). 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 loss of engine power due to fuel flow interruption, which resulted from a stuck carburetor bowl needle.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 21, 2012
- Place
- Lincolnton, North Carolina · Pvt Field · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Aero Works Aero Lite 103
- Registration
- N2355L · no longer on the register · serial A-AWI-121702-127-R50
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that he taxied to the end of the runway, conducted an engine run-up, and prepared for takeoff. He said that the airplane developed full power during the initial climb but that it began to lose power about 300 feet above ground level. He turned back toward the airport and made an emergency landing in vegetation on the side of the runway. The airplane’s right wing was substantially damaged. Postaccident examination revealed that the carburetor bowl needle was stuck in the closed position. The pilot did not report any mechanical malfunctions or failures that would have precluded normal operation.
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
- Fuel starvation during initial climb defining event
- Loss of engine power (partial) during initial climb
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine fuel and control › Fuel control/carburetor › Malfunction
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 537 hours in all; 264 in this make and model; 5 in the last 90 days; 2 in the last 30 days; 490 as pilot in command
- Last flight review: November 8, 2011
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: ctr
- Injury: no injuries
The aircraft
- Airframe total time: 264 hours
- Last inspection: annual inspection, May 18, 2012; 2 hours since
- Maximum gross weight: 630 lb
- Seats: 1
- Landing gear: fixed
- Engine: Rotax 503 (piston); 0 hours total
The flight
- Departed from: Lincolnton NC
- Destination: Lincolnton NC
- Flight plan: not recorded
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 70°F (21°C)
- Altimeter: 29.88 inHg
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.