Temco GC-1B accident near Ewell, Maryland, October 2, 2011
On October 2, 2011 at about 7:13 pm local time, a Temco GC-1B, registered N3825K, was substantially damaged in an accident during enroute (cruise) near Ewell, Maryland. It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper fuel management in that he did not verify the fuel selector position before beginning the flight or after the power loss, which resulted in a total loss of engine power due to fuel starvation and subsequent ditching.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 2, 2011 · about 7:13 pm local time · cases in 2011
- Place
- Ewell, Maryland · map
- Type
- Accident
- Injuries
- 1 person was killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Temco GC-1B · all GC-1Bs on the register
- Registration
- N3825K · no longer on the register · serial 3514
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot made an uneventful 45-minute cross country flight from his home airport to the destination airport. About 10 minutes into the return flight, the airplane was cruising over water at 2,000 feet mean sea level when it experienced a total loss of engine power. The pilot attempted to glide to an island and performed emergency procedures; however, he did not verify the position of the fuel tank selector. The airplane glided about 2 miles before ditching in the water. The airplane was equipped with main and auxiliary fuel tanks that held 26 and 9 gallons of fuel, respectively, and the engine burned about 9 gallons of fuel per hour; the pilot reported that both tanks were full when he departed from his home airport. The pilot further reported that, if he had accidentally left the fuel selector positioned to the auxiliary fuel tank prior to departing his home airport, he would have had just enough fuel to fly the outbound leg, begin the return leg, and lose engine power where he did. When the airplane was recovered, the fuel selector was found positioned to the auxiliary fuel tank. Examination of the wreckage did not reveal any preimpact mechanical malfunctions. In the pilot’s operating handbook for the airplane, the procedure for an engine failure during flight stated that, for airplanes equipped with an auxiliary fuel tank, the pilot should ascertain that the fuel selector valve is on a tank containing fuel.
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 enroute (cruise) defining event
- Ditching during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft systems › Fuel system › Fuel selector/shutoff valve › Incorrect use/operation other cases naming the fuel system
- cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
Pilot
- Certificate: airline transport pilot, commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 6,800 hours in all; 120 in this make and model; 60 in the last 90 days; 30 in the last 30 days; 2,400 as pilot in command; 2,600 on instruments
- Last flight review: June 17, 2010
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 5,005 hours
- Last inspection: annual inspection, March 25, 2011; 35 hours since
- Maximum gross weight: 1,825 lb
- Seats: 2
- Landing gear: retractable
- Engine: Cont Motor O-300 (piston); 0 hours total
The flight
- Departed from: TGI Tangier VA at 7:00 pm
- Destination: W32 Clinton MD
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 250° at 9 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 3,600 ft; a few clouds at 2,000 ft
- Temperature: 52°F (11°C), dew point 43°F (6°C)
- Altimeter: 29.87 inHg
- Observation at 6:52 pm from NHK, 15 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
15 documents, released by the NTSB on July 17, 2012. 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
- N3825K: not on the register today · the record of its deregistration
- Temco GC-1 116 registered today · the model family and its accident history
- Temco 131 aircraft on the register
- Engine: Cont Motor O-300 6,625 aircraft carry this series today · as the NTSB recorded it
- Tangier Island Airport · departed from
- Accidents and incidents in Maryland 837 since 1982 · 111 in the last ten years
- Maryland 2,355 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA12FA002.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.
