19961018045939A

Accident · Destroyed

FAA accident report · Cessna 310Q · Baltimore, MD · October 18, 1996

Date
October 18, 1996 · 23:01 local
Place
Baltimore, MD
Airport
Baltimore-Washington International
Phase of flight
Forced Landing
Operating rules
Air taxi and commuter (Part 135)
Operator
S2VA
Damage
Destroyed
Aircraft
N8226Q
Reported as
Cessna 310Q
Reported engine
Continental IO470VO
People aboard
2
Fatal injuries
0
Pilot’s flight hours
9,640 total600 in this make and model135 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

The pilot departed on the first of three legs with an undetermined amount of fuel. He reported to the passenger that the fuel quantity indicating system was inaccurate, but that he knew how much fuel was on board. After flying two legs and purchasing a total of 50 gallons enroute, the airplane departed with what the pilot estimated was a two-hour fuel load for an anticipated on hour final leg to bwi. The passenger reported that the airplane had intercepted the localizer course for the ILS runway 28 approach at bwi at 3000 feet. He said "all of a sudden the aircraft started yawing violently left to right, because both engines were alternating power, then no power. (The pilot) asked, "which engine is failing?" And I said "they're both failing you're out of fuel." He tried to access fuel in the (auxiliary) tanks but there was no fuel anywhere in the aircraft." Both engines subsequently stopped producing power, and the aircraft descended into wooded terrain. The airplane had been aloft for about 1 hour and 40 minutes when the engines stopped producing power. There was no fuel nor evidence of fuel found at the accident site.

As the FAA filed it

THE PILOT DEPARTED ON THE FIRST OF THREE LEGS WITH AN UNDETERMINED AMOUNT OF FUEL. HE REPORTED TO THE PASSENGER THAT THE FUEL QUANTITY INDICATING SYSTEM WAS INACCURATE, BUT THAT HE KNEW HOW MUCH FUEL WAS ON BOARD. AFTER FLYING TWO LEGS AND PURCHASING A TOTAL OF 50 GALLONS ENROUTE, THE AIRPLANE DEPARTED WITH WHAT THE PILOT ESTIMATED WAS A TWO-HOUR FUEL LOAD FOR AN ANTICIPATED ON HOUR FINAL LEG TO BWI. THE PASSENGER REPORTED THAT THE AIRPLANE HAD INTERCEPTED THE LOCALIZER COURSE FOR THE ILS RUNWAY 28 APPROACH AT BWI AT 3000 FEET. HE SAID "ALL OF A SUDDEN THE AIRCRAFT STARTED YAWING VIOLENTLY LEFT TO RIGHT, BECAUSE BOTH ENGINES WERE ALTERNATING POWER, THEN NO POWER. (THE PILOT) ASKED, "WHICH ENGINE IS FAILING?" AND I SAID "THEY'RE BOTH FAILING YOU'RE OUT OF FUEL." HE TRIED TO ACCESS FUEL IN THE (AUXILIARY) TANKS BUT THERE WAS NO FUEL ANYWHERE IN THE AIRCRAFT." BOTH ENGINES SUBSEQUENTLY STOPPED PRODUCING POWER, AND THE AIRCRAFT DESCENDED INTO WOODED TERRAIN. THE AIRPLANE HAD BEEN ALOFT FOR ABOUT 1 HOUR AND 40 MINUTES WHEN THE ENGINES STOPPED PRODUCING POWER. THERE WAS NO FUEL NOR EVIDENCE OF FUEL FOUND AT THE ACCIDENT SITE.

Other reports on N8226Q · 1

Matched to the same aircraft by N-number and date.