Grant Aviation Cessna 208B accident
Cessna 208B and Hageland Aviation Cessna 208B · Accident: ground collision while taxiing
Event
- NTSB case
- ANC09LA004
- 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
- Charter & commuter
- 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
Aircraft 1 · 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
- N1229C
- Operator
- Grant Aviation
- Onboard fatalities
- Unknown
- Route
- From Emmonak Airport (PAEM), Emmonak, AKTo Bethel Airport (PABE), Bethel, AK
- 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 135: Air Taxi & Commuter
- 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
- Taxi · from runway
- 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
- Ground collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · 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
- N411GV
- Operator
- Hageland Aviation
- Onboard fatalities
- Unknown
- Route
- From Bethel Airport (PABE), Bethel, AKTo St Mary's Airport (PASM), St. Marys, AK
- 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 135: Air Taxi & Commuter
- 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
- Taxi · to runway
- 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
- Ground collision
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
N411GV, a Cessna 208B, was taxiing south on Taxiway C towards the runway. A second Cessna 208B, N1229C, was exiting toward the east from the runway at Taxiway B. The ground controller told N29C, "taxi to park on the right, use caution for company traffic." The controller mistakenly thought the two airplanes were from the same company. No caution was issued to N1GV to move the right to avoid N29C. The left wingtips of each airplane collided at the intersection of Taxiways B and C. The controller did not instruct either airplane to hold or give way to the other, and the intersection was not large enough to accommodate them both at the same time. Each airplane received structural damage to their wingtips and fuselages. The FAA's Air Traffic Controller's Handbook contains instructions and phraseology for use by air traffic controllers to marshal the movement of aircraft on the airport's movement area, and that specific phraseology was not used. Following the accident, the tower manager issued corrective actions for ground operations, which included notifying airport operators of a change in taxiing procedures, training all controllers of new taxiing procedures, and additional phraseology training of the controller involved in the accident. Federal Aviation Regulation (FAR) Part 91.3, notes that the pilot-in-command of an aircraft is directly responsible for, and is the final authority as to the operation of that aircraft. The Aeronautical Information Manual (AIM), notes that although an ATC clearance is issued for taxiing purposes, it is the responsibility of the pilot to avoid collision with other aircraft.
Probable cause
The failure of both pilots to maintain adequate clearance/distance from each other at the taxiway intersection to avoid a collision. Contributing to the accident was a lack of clear and concise instruction to either airplane by the ground controller to preclude them from entering the taxiway intersection at the same time.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC09LA004
- Event ID
- 20081009X70534
- Case number
- ANC09LA004
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2008-10-08.
- API snapshot SHA-256: 5172ffde2a2c9be4bb65346583e4896d626339f36927f06aad8f11f431613db3; retrieved 2026-09-13T18:14:19.789Z.