Grumman American Avn. CORP. AA1B accident near Chester, South Carolina, May 23, 2014
On May 23, 2014 at about 5:00 pm local time, a 1974 Grumman American Avn. CORP. AA1B, registered N8890L, was substantially damaged in an accident during enroute (cruise) near Chester, South Carolina. It was a personal flight 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
The pilot's inadequate inflight fuel monitoring, which resulted in fuel exhaustion and the subsequent total loss of engine power. Contributing to the accident was the loose fuel cap, which allowed fuel to syphon out in flight.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 23, 2014 · about 5:00 pm local time
- Place
- Chester, South Carolina · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Grumman American Avn. CORP. AA1B, built 1974 · all AA1Bs on the register
- Registration
- N8890L · no longer on the register · serial AA1B-0390
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane departed on a cross-country flight after the pilot purchased 11.92 gallons of fuel. A flight plan found in the wreckage with the accident pilot's name on listed the fuel onboard as 3 hours and 30 minutes and a flight distance of 240 miles. The airplane wreckage was located about 130 miles from the departure airport. Postaccident examination of the propeller indicated that the engine was not producing power at impact. Examination of the wreckage and surrounding vegetation revealed no evidence of fuel within the fuel tanks and only slight amounts of blight, consistent with fuel spillage, on nearby vegetation at the accident site. Fuel staining was observed on the right wing, and the fuel cap did not have a detent. If the pilot had performed a preflight inspection of the airplane before departure, he would have noticed the fuel staining; thus it likely occurred during the accident flight, although it could not be determined why the pilot did not notice the loose fuel cap. Given the distance flown and cruise speed, the airplane's published fuel consumption indicates that the airplane would have consumed about 11 gallons of fuel in the 90 minutes of flight. Although both fuel tanks likely contained enough fuel for a flight longer than 90 minutes at takeoff, it is likely that any fuel in the right fuel tank was syphoned out during flight due to the loose fuel cap. Even though the estimated fuel consumption calculations showed that the total quantity consumed was less than what was indicated the flight plan, the lack of fuel observed at the accident site and the lack of evidence of any preexisting mechanical anomalies indicate that the total loss of engine power was likely the result of fuel exhaustion. Although the fuel selector valve's Teflon plunger was found fractured, which resulted in the selector valve binding, the fracture was consistent with impact damage. The airplane was not reported overdue for several days and was located in a wooded area about 3 days after it had departed. The airplane's emergency locator transmitter (ELT) unit had an "ON/OFF/ARM" switch that was found in the "OFF" position. The ELT may have been deactivated by first responders; however, given that there were no reports of ELT signals being detected in the area from the day of the accident until the airplane was located, the ELT was likely in the "OFF" position before the flight and did not activate due to the switch position, which delayed the search and rescue of the occupants.
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
- Preflight or dispatch event during prior to flight
- Fuel exhaustion during enroute (cruise) defining event
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
- cause Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot
- cause Personnel issues › Action/decision › Action › Lack of action › Pilot
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
- factor Personnel issues › Task performance › Inspection › Preflight inspection › Pilot
- factor Aircraft › Aircraft systems › Fuel system › (general) › Incorrect use/operation
- Aircraft › Aircraft systems › Equipment/furnishings › Emergency equipment › Inadequate inspection
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
- Flight time: 281.2 hours in all; 9.5 in this make and model; 0.8 in the last 90 days; 0.8 in the last 30 days
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 2,258 hours
- Last inspection: 100-hour inspection, May 23, 2014; 3 hours since
- Maximum gross weight: 1,561 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-235-C2C (piston); 2,258 hours total
- Operator: Warriors To Wings Aero Club
The flight
- Departed from: CPC Whiteville NC at 3:30 pm
- Destination: GE99 Clayton GA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 310° at 8 knots
- Visibility: 7 statute miles
- Sky: clear
- Temperature: 90°F (32°C), dew point 61°F (16°C)
- Altimeter: 30.03 inHg
- Observation at 4:55 pm from DCM, 8 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
16 documents, released by the NTSB on April 14, 2015. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot Logbook | PDF, 6 pages | View Download |
| 2 | Email from Usmc - Pilot Flight Time | PDF, 1 page | View Download |
| 3 | Electronic Devices - Specialist's Factual Report | PDF, 3 pages | View Download |
| 4 | radar Data | PDF, 3 pages | View Download |
| 5 | radar Source Data | spreadsheet | Download |
| 6 | Flight Plan | PDF, 1 page | View Download |
| 7 | Lockheed Martin Email | PDF, 1 page | View Download |
| 8 | Fuel Receipt | PDF, 1 page | View Download |
| 9 | Maintenance Records (Excerpts) | PDF, 4 pages | View Download |
| 10 | AA1B Owners Manual (Excerpts) | PDF, 3 pages | View Download |
| 11 | Lycoming Fuel Flow Numbers | PDF, 1 page | View Download |
| 12 | Memorandum of Record - Flying Club Representative and Mechanic | PDF, 1 page | View Download |
| 13 | Memorandum of Record - Chester South Carolina Weather | PDF, 2 pages | View Download |
| 14 | Toxicological Report | PDF, 2 pages | View Download |
| 15 | Statement of Party Representatives to NTSB Investigation | PDF, 14 pages | View Download |
| 16 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
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.
