# Accident 20041208030759A: Beech B200, Tulsa, OK, December 8, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 8, 2004, 18:31 local time
- Place: Tulsa, OK
- Airport: Tulsa International
- Damage: Substantial damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 36.2792° N, 95.8861° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.2792&lon=-95.8861&mi=10
- Aircraft: N6PE, a cancelled registration (https://openairdocs.org/deregistered/N6PE-2005-05-05) (OpenAirDocs)
- Registry model: Beech B200 (registry code 1152922, https://openairdocs.org/model/beech-b200) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada PT6A-60A (registry code 52043, https://openairdocs.org/engine/pratt-whitney-canada-pt6a-60a) (OpenAirDocs)
- Reported make and model: BEECH B200
- Fatal injuries: 0
- Pilot flight hours: 2,089 total, 469 in this make and model, 60 in the last 90 days
- NTSB investigation: [NTSB DFW05LA031](https://openairdocs.org/ntsb/DFW05LA031) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041208030759A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON DECEMBER 8, 2004, AT APPROXIMATELY 1831 CST, A BE-200 CRASHED LANDED ON 86TH ST. NORTH, 4 MILES NORTH OF TULSA INTERNATIONAL AIRPORT (TUL). THE PILOT HAD DEPARTED LACROSSE WISCONSIN (LSE) AT APPROXIMATELY 1605 CST BOUND FOR TUL. WHEN NEARING HIS DESTINATION THE PILOT CONTACTED TUL APPROACH FOR LANDING INSTRUCTIONS, SHORTLY AFTER THAT HE CONTACTED THEM AGAIN TO DECLARE AN EMERGENCY STATING THAT HE HAD LOST BOTH ENGINES. ATC DIRECTED THE PILOT TO LAND ON RWY 18L AND ASKED HIM HOW MANY WERE ON BOARD AND WHAT WAS HIS FUEL QUANTITY. THE PILOT STATED ONE ON BOARD AND FUEL OK, THEN CORRECTED HIMSELF AND SAID FUEL EMPTY. SHORTLY THEREAFTER THE PILOT DECIDED HE COULD NOT MAKE IT TO THE AIRPORT, HE THEN SPOTTED AN EAST/WEST ROAD AND MADE A RIGHT TURN AND CONTINUED TO DESCEND. WHEN NEARING THE ROAD THE RIGHT WING CONTACTED POWER LINES AND THE LEFT WING BEGAN TO IMPACT TREE LIMBS, SHORTLY AFTER LANDING WITH THE GEAR UP THE AIRCRAFT SLID WITH THE LEFT ENGINE PROPELLER IMPACTING A TREE AND THE NOSE IMPACTING AN EMBANKMENT ON THE SOUTH SIDE OF THE ROAD. THE AIRCRAFT CONTINUED TO SLIDE AND SPIN WITH THE RIGHT WING ALSO HITTING THE SOUTH EMBANKMENT. THE AIRCRAFT CAME TO REST FACING NORTH WITH THE NOSE CONTACTING THE EMBANKMENT ON THE NORTH SIDE OF THE ROAD. THE ENGINES, PROPELLERS, WINGS AND TAIL WERE SUBSTANTIALLY DAMAGED. THE TAIL WAS MOSTLY SEPARATED AT THE REAR BULKHEAD AND THE NOSE HAD MAJOR DAMAGE ALSO. THE LEFT/RIGHT WING INBOARD MAIN, NACELLE, AND AUX FUEL SUMPS WERE DRAINED, AND IT WAS DISCOVERED THAT THE ONLY TANK WITH USABLE FUEL WAS THE LEFT NACELLE, IT HAD APPROX 4 GALLONS. AFTER REPORTING THE EMERGENCY TO ATC, THE PILOT WAS QUESTIONED BY ATC AS TO AMOUNT OF FUEL ON BOARD, TO WHICH HIS REPLY WAS "ITS READING EMPTY." ALSO, IT WAS INITIALLY DISCOVERED THE FUEL CROSSFEED FLOW SWITCH WAS IN THE LEFT POSITION. THE AIRCRAFT TRAVELED APPROXIMATELY 360 FEET FROM INITIAL CONTACT WITH THE POWER LINES AND TREES UNTIL IT CAME TO STOP. THERE WAS NO POST IMPACT FIRE AND ONLY VERY LIMITED TRACES OF FUEL COULD BE FOUND AT THE SCENE. THE PILOT WAS THE ONLY ONE ON BOARD AND HE ONLY SUSTAINED MINOR INJURIES.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DFW05LA031](https://openairdocs.org/ntsb/DFW05LA031), Dec 9, 2004: Beech B200 (N6PE), Tulsa, OK, substantial damage. Probable cause: The loss of engine power due to fuel exhaustion as a result of the pilot's inadequate preflight and in-flight planning / preparation.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.