NYC06FA079 · Beech 56TC
Beech 56TC · Accident en route
From Dawson Community Airport (GDV) to Saint Paul Downtown Holman Field (STP)
Event
- NTSB case
- NYC06FA079
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech 56TC
- Aircraft type
- Beechcraft 56
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N18LL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dawson Community Airport (GDV), Glendive, MTTo Saint Paul Downtown Holman Field (STP), St. Paul, MN
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Miscellaneous/other
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Oxygen system › Exhaustion
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While on the last leg of a multiple day cross-country trip, all communications between the pilot of a non-pressurized, oxygen system equipped airplane, and air traffic control (ATC) were normal until the airplane was detected to have climbed 400 feet above its assigned altitude of FL240. After being notified of the deviation, the pilot responded that he was attempting to look at his contrails. Later in the flight, after leveling at FL270, the pilot queried ATC as to whether they had heard some of his previous calls. This was the last transmission received from the pilot, and attempts to reestablish contact were unsuccessful. After the pilot had not begun his descent for landing, nor joined the arrival course for his destination, ATC requested assistance from the North American Aerospace Defense Command (NORAD). After intercepting the airplane, the pilots of the fighter airplanes attempted to look into the cockpit, but were unable to see the pilot. Attempts to gain his attention were also unsuccessful. The airplane eventually descended and impacted terrain. A nasal cannula was connected to the airplane's installed oxygen system and was found near the pilot. An oxygen mask the pilot was wearing was connected to a portable oxygen bottle found on the floor next to him. Both systems were functional, their valves were open, and both were depleted of their contents. The portable bottle was manufactured for industrial use, and modified with an oxygen system fitting. The regulator was manufactured for the medical industry. A review of a journal kept by the pilot revealed that he flew at high altitudes for efficiency, and used an oximeter to monitor blood oxygen. He used a nasal cannula at altitudes exceeding 18,000 feet for comfort, and had used a "cannula and mask" up to 31,000 feet. Examination of his hangar revealed an aircraft oxygen tank and welding tank plumbed to an oxygen-service fitting. The airplane's oxygen system or portable bottle had not been serviced at the airports the airplane operated from during the trip. According to Advisory Circular (AC) 61-107A, "Operations of Aircraft At Altitudes Above 25,000 Feet MSL And/Or Mach Numbers (MMO) Greater Than .75", preflight inspections should include a thorough examination of aircraft oxygen equipment, "including available supply," and that "Oxygen systems should be checked periodically to ensure that there is an adequate supply of oxygen and that the system is functioning properly. This check should be performed frequently with increasing altitude. If supplemental oxygen is not available, an emergency descent to an altitude below 10,000 feet should be initiated." Additionally, it advised that when using continuous flow oxygen systems above 25,000 feet, "very careful attention to system capabilities is required."
Probable cause
The pilot's inadequate preflight preparation to ensure an adequate supply of supplemental oxygen, and his inadequate in-flight planning and decision making, which resulted in exhaustion of his oxygen supply, and incapacitation from hypoxia during cruise flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06FA079
- Event ID
- 20060331X00370
- Case number
- NYC06FA079
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-03-18.
- API snapshot SHA-256: 1b26cd47b1a09764568b6032600dbb137553b4571da10922238c61657453b510; retrieved 2026-09-20T17:29:41.059Z.