Cessna 180 accident near Nome, Alaska, July 4, 2016
On July 4, 2016 at about 4:30 am local time, a 1960 Cessna 180, registered N9203T, was substantially damaged in an accident during landing near Nome, Alaska (Nome City Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain an adequate glide path during landing, which resulted in the airplane landing short of the runway and impacting a barricade. Contributing to the accident was the airport manager's improper placement and marking of a metal barricade that encroached on the runway safety area.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 4, 2016 · about 4:30 am local time · cases in 2016
- Place
- Nome, Alaska · Nome City Field · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 180 C, built 1960 · all 180s on the register
- Registration
- N9203T · registry record · serial 50703
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that while landing on a gravel surfaced runway in a tailwheel-equipped airplane, a downdraft was encountered, which forced the airplane to the ground prematurely. The airplane subsequently impacted an estimated 38-inch-high metal barricade that was located about 90 feet from the runway threshold resulting in substantial damage to the right wing lift strut The pilot stated that there were no preaccident mechanical malfunctions or anomalies with the airplane that would have precluded normal operation. The airport manager stated that the metal barricade sections were erected each summer season to prevent All-Terrain Vehicles from using the runway, thus mitigating runway incursions.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Landing area undershoot during landing defining event
- Collision with terrain or object (not controlled flight into terrain) during landing
- Airport occurrence during landing
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Environmental issues › Physical environment › Object/animal/substance › Wall/barricade › Effect on operation
- factor Personnel issues › Action/decision › Action › (general) › Airport personnel
- Environmental issues › Physical environment › Object/animal/substance › Wall/barricade › Awareness of condition
Pilot
- Certificate: private
- Ratings: single-engine land; single-engine sea
- Flight time: 537 hours in all; 266 in this make and model; 11 in the last 90 days; 11 in the last 30 days; 484 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 5,119 hours
- Last inspection: annual inspection, June 23, 2015
- Seats: 3
- Landing gear: fixed
- Engine: Lycoming O&VO-360 SER (piston); 0 hours total
The flight
- Departed from: 5QC Quartz Creek AK at 10:55 pm
- Destination: 94Z Nome AK
- Flight plan: VFR
- Runway 21, 1,950 ft by 110 ft
Weather at the time
- Light: daylight
- Wind: from 260° at 20 knots, gusting 29
- Visibility: 10 statute miles
- Sky: broken clouds at 28,000 ft; a few clouds at 400 ft
- Temperature: 52°F (11°C), dew point 45°F (7°C)
- Altimeter: 29.80 inHg
- Observation at 3:53 am from PAOM, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on August 30, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Record of Conversation, Airport Manager | PDF, 1 page | View Download |
| 2 | Airport Manager Statement | PDF, 1 page | View Download |
| 3 | Record of Conversation, Pilot | PDF, 1 page | View Download |
| 4 | Accident Photographs (Courtesy of FAA and Airport Manager) | PDF, 4 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N9203T on the register today · the tail number may have moved to another aircraft since
- Cessna 180 Skywagon 2,603 registered today · the model family and its accident history
- Cessna 72,673 aircraft on the register
- Engine: Lycoming O&VO-360 SER · as the NTSB recorded it
- Nome City Field · nearest airport
- Quartz Creek / Kougarok Airport · departed from
- Accidents and incidents in Alaska 5,932 since 1982 · 823 in the last ten years
- Alaska 9,148 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ANC16CA040.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.