FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07LA063 · Raytheon Aircraft Company B200

2 Feb 2007 · Cape Girardeau, MO, United States

Raytheon Aircraft Company B200 · Accident: decompression en route

From Rogers Municipal Airport-Carter Field (ROG) to Shenandoah Valley Regional Airport (SHD)

Report a problem

Event

NTSB case
CHI07LA063
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
0 · 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

Raytheon Aircraft Company B200

Aircraft type
Beechcraft 200
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
N777AJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rogers Municipal Airport-Carter Field (ROG), Rogers, ARTo Shenandoah Valley Regional Airport (SHD), Staunton, VA
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
Decompression
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

  • Flightcrew › Incapacitation(loss of consciousness)
  • Pilot in command › Improper use of procedure

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was operated by a company pilot. A noncompany pilot, who had not attended or completed a training course or received a checkout for Raytheon Aircraft Company Beech King Air 200 airplanes, was asked by the pilot to accompany him on the flight so that the noncompany pilot could accumulate flight time. The flight only required one pilot.

While the airplane was in cruise flight (27,000 feet mean sea level), the cockpit voice recorder (CVR) recorded the sound of the windshield fracturing. The CVR transcript indicated that the company pilot was not in the cockpit when the windshield fractured because he was emptying trash in the cabin. This action showed poor judgment considering the noncompany pilot was not qualified in the airplane.

Although the windshield stayed in place, the company pilot stated that "within seconds" after it fractured, he depressurized the airplane because he was unsure about the windshield's "integrity." However, the Beech King Air Airplane Flight Manual (AFM) states to maintain cabin pressurization in the event of a fractured windshield and further states that the airplane can continue flight for up to 25 hours with the windshield fractured. During the on-scene examinations, an unapproved document (not derived from the AFM) that contained several checklists was found on the airplane. The company pilot stated that he used this document and that it "came with the airplane." The document did not include a checklist addressing a cracked or shattered windshield. The company pilot most likely was not aware that the airplane should not have been depressurized nor that it could operate for 25 hours after the fracture occurred and, therefore, that the fractured windshield did not present an in-flight emergency.

The CVR transcript revealed that, after depressurizing the airplane, the pilots attempted to use the oxygen masks but were unable to receive any oxygen. (The pilots most likely did not turn the oxygen on once they needed it because they either forgot as a result of the emergency or because they did not have time to do so before they lost consciousness.) According to the company pilot, during his preflight inspection of the airplane, the oxygen system was functional. He stated that, after the inspection, he turned the oxygen system ready switch to the OFF position because he wanted to "save" the oxygen, which was not in accordance with the Before Start checklist in the AFM. Postaccident functional testing of the oxygen system revealed normal operation. The unapproved checklists document did not include the instruction to leave the oxygen system on. Regardless, the pilot stated that he knew the approved checklist stated to leave the oxygen system on but that he still chose to turn it off. The pilot exhibited poor judgment by using an unapproved, incomplete checklists document and by knowingly deviating from approved preflight procedures.

About 1 minute after the pilots tried to get oxygen, the CVR recorded the last comment by either pilot. For about the next 7 minutes until it stopped recording, the CVR recorded the sounds of increased engine propeller noise, the landing gear and overspeed warning horns, and altitude alerts indicating that the airplane had entered an uncontrolled descent. (The CVR's 4-g impact switch was found in the open position during the on-scene examination, indicating that the airplane experienced at least 4 acceleration of gravity forces.) Further, a plot of two radar data points, recorded after the last pilot comment, showed that the airplane descended from 25,400 feet to 7,800 feet within 5 minutes. Shortly thereafter, the pilots regained consciousness and recovered from the uncontrolled descent. The airplane was substantially damaged by the acceleration forces incurred during the uncontrolled descent and subsequent recovery.

Examination of the windshield revealed that a dense network of fractures was located on the inner glass ply; however, the windshield did not lose significant pieces of glass and maintained its structural integrity. Therefore, the fractures did not preclude safe continued flight. Postaccident examinations revealed evidence that the fracture initiated due to a design deficiency in the glass. The manufacturer redesigned the windshield in 2001 (the accident airplane was manufactured in 1998), and no known similar fractures have occurred in the newly designed windshield. The manufacturer chose not to issue a service bulletin for a retrofit of the new windshield design in airplanes manufactured before 2001 because the fracture of one pane of glass is not a safety-of-flight issue.

Members Hersman and Sumwalt did not approve this brief. Member Hersman filed a dissenting statement, with which Member Sumwalt concurred. The statement can be found in the public docket for this accident.

Probable cause

The company pilot's poor judgment before and during the flight, including turning the oxygen system ready switch to the OFF position after he conducted the preflight inspection and using an unapproved checklist, which did not provide guidance for a fractured windshield and resulted in his depressurizing the airplane.

Members Hersman and Sumwalt did not approve this probable cause. Member Hersman filed a dissenting statement, with which Member Sumwalt concurred. The statement can be found in the public docket for this accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07LA063
Event ID
20070208X00156
Case number
CHI07LA063
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 51293ce460c4d8bc25e9189abd9c6f67a554f8881ae3b376eee6dd68552a1035; retrieved 2026-09-22T04:03:17.952Z.