SEA08LA082 · Raytheon Aircraft Company 1900D
Raytheon Aircraft Company 1900D · Accident: runway excursion during landing
From Flagstaff Pulliam Airport (FLG) to Exceptional Community Hospital Heliport (38AZ)
Event
- NTSB case
- SEA08LA082
- 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
- Instrument Meteorological Cond
Raytheon Aircraft Company 1900D
- Aircraft type
- Beechcraft 1900
- 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
- N305PC
- Operator
- Peabody Energy
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo Exceptional Community Hospital Heliport (38AZ), Kayenta, AZ
- 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
- Landing · landing roll
- Defining eventThe 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
- Runway excursion
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The captain initially flew the GPS (global positioning system) runway 2 approach down to minimums and executed a missed approach. The approach chart listed the minimum visibility for the straight-in approach as 1 mile, the minimum descent altitude (MDA) as 6,860 feet mean sea level (329 feet above ground level), and the missed approach point as the runway threshold. The audio information extracted from the CVR indicated the flight crew listened to the automated weather station at the airport twice during the second approach; both times the report stated, in part, "visibility one half [mile] light snow sky conditions ceiling two hundred broken one thousand overcast." At 0744:09, the first officer said, "there's MDA," and at 0744:27, "there's the runway right below ya." The CVR recorded the ground proximity warning system (GPWS) audio alert "sink rate, sink rate, sink rate, sink rate" at 0744:37, the sound of touchdown at 0744:52, and the sound of impact at 0745:00. According to both pilots, the airplane touched down even with the midfield windsock. The captain applied brakes and full reverse on both propellers; however, the airplane did not slow down and continued off the end of the runway, impacted and knocked down a chain link fence, and continued into downsloping rough terrain. The landing gear collapsed and the airplane slid to a stop. The operator reported that there was 2 to 3 inches of slush on the runway. The runway was equipped with pilot activated medium intensity runway lights, runway end identifier lights, and a visual approach slope indicator. The first officer said that on both approaches, he attempted to turn on the lights, but the lights did not activate. The Federal Aviation Regulation that specifies the instrument flight rules for takeoff and landing states, in part, that no pilot may operate an aircraft below the authorized MDA unless (1) the aircraft is continuously in a position from which a descent to a landing on the intended runway can be made at a normal rate of descent using normal maneuvers, and (2) the flight visibility is not less than the visibility prescribed in the standard instrument approach being used. The regulation further states that if these conditions are not met when the aircraft is being operated below the MDA or upon arrival at the missed approach point, the pilot shall immediately execute an appropriate missed approach procedure. In this case, the minimum required visibility was 1 mile versus the 1/2-mile visibility reported by the automated weather station. Additionally, the activation of the GPWS "sink rate" audio alert indicates a normal rate of descent was exceeded during the landing. Both of these conditions should have prompted the flight crew to execute a missed approach, which would have prevented the accident.
Probable cause
The flight crew's failure to execute a missed approach, which resulted in a runway excursion after landing. Contributing to the accident were the inoperative lights, weather conditions below published approach minimums, and the slush contaminated runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA08LA082
- Event ID
- 20080228X00245
- Case number
- SEA08LA082
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: b34dd700153af81570c4f756e3fed0260a84ee42b91eb873b9a2e9876eadac0b; retrieved 2026-09-15T09:23:37.071Z.