FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Grant Aviation Cessna 207A accident

3 Sept 2010 · Tuluksak, AK, United States

Cessna 207A · Accident: collision during takeoff/landing

From Tuluksak Airport (TLT) to an unrecorded destination

Report a problem

Event

NTSB case
ANC10LA083
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

Cessna 207A

Aircraft type
Cessna 207
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
N9942M
Onboard fatalities
Unknown
Route
From Tuluksak Airport (TLT), Tuluksak, AKTo not recorded
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
Takeoff
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
Collision during takeoff/landing
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The director of operations for the operator stated that soft field conditions and standing water on the runway slowed the airplane during the takeoff roll. The airplane did not lift off in time to clear trees at the end of the runway and sustained substantial damage to both wings and the fuselage when it collided with the trees. The pilot reported that he used partial power at the beginning of the takeoff roll to avoid hitting standing water on the runway with full power. After passing most of the water, he applied full power, but the airplane did not accelerate like he thought it would. He recalled the airplane being in a nose-high attitude and the main wheels bouncing several times before the airplane impacted the trees at the end of the runway.

Probable cause

The pilot's delayed application of full power during a soft/wet field takeoff, resulting in a collision with trees during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC10LA083
Event ID
20100908X65810
Case number
ANC10LA083
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-09-04.
  • API snapshot SHA-256: a6d9cd85519437a50d1d21d3e0a0d1beb9a9b9749ed834846691673c11224755; retrieved 2026-09-15T15:08:18.924Z.