FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC23FA042 · Cessna 180 H

16 Jun 2023 · Shaktoolik, AK, United States

Cessna 180 H · Accident: collision during takeoff/landing during initial climb

From Unalakleet Airport (PAUN) to Unalakleet Airport (PAUN)

Report a problem

Event

NTSB case
ANC23FA042
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
2 · 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 180 H

Aircraft type
Cessna 180
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
N91361
Operator
James B. Tweto · private individual
Onboard fatalities
Unknown
Route
From Unalakleet Airport (PAUN), Unalakleet, AKTo Unalakleet Airport (PAUN), Unalakleet, AK
Aircraft age
About 54 years (built 1969)
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
Initial climb
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
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
Tree(s)
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

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • 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 pilot and passenger were departing downhill in a southwesterly direction from a remote, sloped airstrip located on a mountain ridgeline. According to a witness, the pilot had three trips planned to the airstrip that day, transporting hunters and gear to a nearby village. The witness stated that, upon the pilot’s return to the airstrip following the first flight of the day, he reported to the pilot that, since his previous departure, the winds had increased and were “gusting and changing a lot.” He watched the initial portion of the takeoff roll; nothing appeared abnormal, and he did not watch the remainder of the takeoff. He stated that, during previous departures, the airplane would typically dip out of sight below the departure end of the airstrip before continuing its climb out of the valley. When he did not see the airplane continue the climb, he went to the edge of the ridgeline and saw that the airplane had impacted tundra about 300 ft below the airstrip. A small cluster of trees was present about 2/3 of the way down the left side of the 750-ft-long airstrip. One tree was fractured and displayed fragments of red paint that matched the accident airplane’s paint color. The left horizontal stabilizer displayed a concave dent perpendicular to the leading edge about 1 ft outboard of the stabilizer root. Tree sap and embedded tree fibers were observed in the leading edge of the horizontal stabilizer. Examination of the airframe and engine revealed no evidence of any preimpact mechanical failures or malfunctions that would have precluded normal operation. Review of weather information indicated the presence of north/northeasterly surface wind conditions in the area of the accident site. Another pilot, who responded to the accident site about 45 minutes after the accident, reported that the wind was “unusual” and variable, gusting 10-12 knots from the north before gusting 5 knots from the south and repeating. Based on the available information, it is likely that the pilot encountered gusting tailwind conditions during the takeoff, which resulted in the airplane veering left and impacting a tree, followed by a loss of control and impact with terrain.

Probable cause

The pilot’s encounter with gusting tailwind conditions during takeoff, which resulted in impact with a tree, a loss of control, and subsequent impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC23FA042
Event ID
20230616192387
Case number
ANC23FA042
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, cause areas. 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: 2ce0eb486ca3e2d77f754285f047e5114ce83068d89feb48d3251568aaf7d4fd; retrieved 2026-09-15T08:01:26.599Z.