FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

2007 Kapowsin Air Sports accident

7 Oct 2007 · about 55 km west-southwest of Naches, Washington, United States

Cessna 208B · Loss of control after partial incapacitation of the pilot as a result of hypoxia

From Foster Field - Dzone Skydiving Airport (ID92) to Sanderson Field (SHN)

Report a problem

Event

NTSB case
LAX08MA007
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
Unknown
Event fatalities
10 · all aircraft and ground
Ground fatalities
Unknown
Occupants
Unknown
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
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
Instrument Meteorological Cond

Cessna 208B

Aircraft type
Cessna 208
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
N430A
Onboard fatalities
Unknown
Route
From Foster Field - Dzone Skydiving Airport (ID92), Star, IDTo Sanderson Field (SHN), Shelton, WA
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
Maneuvering
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
In flight encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Stall/spin, encountered

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

From the Wikipedia article

The 2007 Kapowsin Air Sports accident occurred on 7 October 2007, when a Cessna 208 Caravan on a flight from Star-Snake River Skydiving Airport in Idaho to Sheldon-Sanderson Field, Washington went out of control and crashed 55 kilometres west-southwest of Naches, Washington. All 10 occupants of the aircraft were killed in the accident.

Accident sequence

After a weekend trip, the group of nine parachutists and the pilot were on their way back to their skydiving base at Shelton-Sanderson Field in the US state of Washington. The pilot had flown several skydiving flights that day and had landed in the early afternoon at Star-Snake River Parachuting Airport in the US state of Idaho to prepare the aircraft for the flight home. The Cessna was to fly through a weather zone in which cloud layers, turbulence and icing conditions were to be expected, which is why the pilot obtained comprehensive information about the weather along the route. He delayed the departure until the weather conditions had improved to the point that he assumed he could conduct the flight under visual flight rules. The aircraft took off from Snake River Skydiving Airport in Star, Idaho at 17:50 local time. About two hours later the aircraft was in the airspace of the state of Washington; it was dark, and that evening the moon illuminated the area only slightly because of the cloud layers through which the aircraft was flying. According to the satellite images and the cockpit voice recorder recordings, the aircraft most probably flew through an area with a broken or overcast cloud layer that extended below and above its flight altitude. There had probably also been lee waves in the area, which could be accompanied by icing conditions. The recorded radar data suggested that the pilot probably tried to manoeuvre the aircraft above, below or around the side of the cloud layer in order to fly out of the rain clouds. He had evidently done this while trying to continue the flight under visual flight conditions. The aircraft probably entered a cloud layer within the last three minutes of flight and was possibly exposed to icing conditions and turbulence. Control of the aircraft was lost shortly thereafter.

Accident investigation

After the accident, the National Transportation Safety Board (NTSB) took over the investigation into the cause of the crash. The accident investigation found that the aircraft's angle of attack had increased significantly within a few moments immediately before the crash. The performance data indicated a stall. The aircraft, which by design did not have a pressurised cabin, had maintained an altitude of 14,000 feet for an hour. Immediately before the crash, after successively flown 360-degree turns in which the aircraft climbed and descended again, it had reached altitudes of 15,000 feet. No oxygen equipment was used on the flight. At such altitudes, pilots can suffer hypoxia without experiencing noticeable symptoms of it. The pilot was certified only for visual flights.

The NTSB concluded that the most probable cause of the accident had been the pilot's failure to maintain sufficient airspeed while manoeuvring the aircraft to avert a stall. Contributing factors were given as his possible partial incapacitation due to hypoxia, as well as knowingly flying through an area in which adverse weather conditions prevailed. Clouds, turbulence and darkness, which suggested that instrument flying had been called for but not carried out, had also contributed to the circumstances of the accident.

Translated into English with AI assistance from the German Wikipedia article “Flugunfall der Kapowsin Air Sports 2007” (revision 252303581, retrieved 2026-09-19) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out; the translation may contain errors, and long articles were cut to their first 700 words. Read the article

NTSB narrative

The pilot was returning a group of skydivers to their home base after a weekend of skydiving. He flew several jump flights, and then stopped early in the afternoon to prepare the airplane for the flight home. The flight was planned into an area of clouds, turbulence, and icing, which the pilot had researched. He delayed the departure until he decided that he could complete the planned flight under visual flight rules (VFR). The accident occurred at night with little illumination of the moon, and the airplane was in an area of layered clouds. A detailed analysis of the weather conditions revealed that the flight probably encountered broken to overcast layers both below and above its flight altitude. The satellite and sounding images suggested that it was possibly in an area of mountain wave conditions, which can enhance icing. The recorded radar data indicated that the pilot was likely maneuvering to go around, above, or below rain showers or clouds while attempting to maintain VFR. The airplane likely entered clouds during the last 3 minutes of flight, and possibly icing and turbulence. It was turning when it departed from controlled flight, and a performance study showed that the angle-of-attack at this point in the flight was increasing rapidly. The study determined that the departure from controlled flight was consistent with an aerodynamic stall. The unpressurized airplane was flying at over 14,000 feet mean sea level for more than 1 hour during the flight. It reached 15,000 feet just prior to the accident in sequential 360-degree turns while climbing and descending. Supplemental oxygen was not being used. At these altitudes, the pilot would be substantially impaired by hypoxia, but would have virtually no subjective symptoms, and would likely be unaware of his impairment. The pilot had logged over 2,000 hours of total flight time, with nearly 300 hours in this make and model of airplane. He was instrument-rated, but had only logged a total of 2 hours of actual instrument flight time. Company policy was to fly under visual flight rules only, and they had not flight-checked the pilot for instrument flight.

Probable cause

The pilot's failure to maintain an adequate airspeed to avoid an aerodynamic stall while maneuvering. Contributing to the accident were the pilot's impaired physiological state due to hypoxia, the pilot's inadequate preflight weather evaluation, and his attempted flight into areas of known adverse weather. Also contributing were the pilot's inadvertent flight into instrument meteorological conditions that included clouds, turbulence, and dark night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

German Wikipedia article: Flugunfall der Kapowsin Air Sports 2007
Article
Flugunfall der Kapowsin Air Sports 2007
Translation
Into English with AI assistance; names of linked operators and aircraft types from Wikidata. It may contain errors.
Revision
252303581 · 2025-01-16 · retrieved 2026-09-19
Wikidata
Q108000327
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record LAX08MA007
Event ID
20071017X01609
Case number
LAX08MA007
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
de Wikipedia article "Flugunfall der Kapowsin Air Sports 2007" (page 11742903, revision 252303581), translated into English with AI assistance; merged with NTSB case LAX08MA007 (events / aircraft)
Date
Wikipedia infobox: date (local date; NTSB record LAX08MA007 stores the UTC date 2007-10-08)
Place and country
Wikipedia infobox: site; country from NTSB record LAX08MA007
Map position
NTSB record LAX08MA007: events decimal coordinates
Aircraft, operator and route
NTSB record LAX08MA007: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record LAX08MA007: operated under Part 91: General Aviation
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities (the NTSB record states no total)
Ground fatalities
NTSB record LAX08MA007: events.inj_f_grnd
Summary
Wikipedia article lead
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "2007 Kapowsin Air Sports accident" and NTSB case LAX08MA007, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • The NTSB record dates it 2007-10-08, the UTC date it stores; the local date, 2007-10-07, is the Wikipedia article's and is used.