FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Warbelow'S Air Ventures Cessna 207A accident

10 Sept 1998 · HUGHES, AK, United States

Cessna 207A · Accident: hard landing

From Edward G. Pitka Sr Airport (PAGA) to Indian Mountain LRRS Airport (PAIM)

Report a problem

Event

NTSB case
ANC98LA150
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
0
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
N7380U
Onboard fatalities
Unknown
Route
From Edward G. Pitka Sr Airport (PAGA), GALENA, AKTo Indian Mountain LRRS Airport (PAIM)
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
Landing · flare/touchdown
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
Hard landing
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
Stall
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

  • Pilot in command › Compensation for wind conditions, inadequate
  • Pilot in command › Stall, inadvertent

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

NTSB narrative

The certificated airline transport pilot was landing in an uphill direction at a remote airport as part of an on-demand air taxi flight. The runway was 4,100 feet long, and 120 feet wide, with an uphill gradient of 7.1 percent. For the runway selected by the pilot, a tail wind of 20 knots, with gusts to 24 knots, was present. During the landing flare, about 3 feet above the runway, the pilot said he encountered a gust of wind, or wind shear. The airplane stalled, and contacted the runway hard on the main landing gear. After landing, the pilot reported he inspected the airplane for damage but did not notice any. The following day, the pilot noticed the aft tie-down ring, and tail skid, located on the underside of the tail cone, was broken off the airplane. In addition, the airplane received damage to the aft empennage bulkhead, and adjacent fuselage structure.

Probable cause

The pilot's inadequate compensation for the wind conditions, and an inadvertent stall. A factor in the accident was the presence of a tail wind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC98LA150
Event ID
20001211X10982
Case number
ANC98LA150
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. 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: 2c213ea018f8ec264ad45de64ff6e52db69e7225787f9e59b2ba25e270482731; retrieved 2026-09-18T17:05:13.937Z.