ANC82DAA09 · Cessna 182
Cessna 182 · Accident: in flight collision with object during landing
From Fairbanks, AK to FT. YUKON, AK
Event
- NTSB case
- ANC82DAA09
- 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
- General aviation
- 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 182
- Aircraft type
- Cessna 182
- 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
- N52763
- Operator
- Hugo T. Ruberg · private individual
- Onboard fatalities
- Unknown
- Route
- From Fairbanks, AKTo FT. YUKON, 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 91: General Aviation
- 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
- In flight collision with object
- 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 › In-flight planning/decision, improper
- Pilot in command › Procedures/directives, not understood
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Estimated position: the centre of Fort Yukon, AK, the place the record names. Not the accident site.
NTSB narrative
THE PILOT STATED THAT HE OVERFLEW THE FT. YUKON AIRPORT AND OBSERVED MEN WORKING ON RUNWAY 21. HE FLEW A DOWNWIND PATTERN FOR RUNWAY 03. WHILE ON FINAL APPROACH TO RUNWAY 03 THE PILOT OBSERVED AN "X" ON THE END OF THE RUNWAY THE PILOT ATTEMPTED A LANDING OFF THE LEFT SIDE OF THE RUNWAY AND COLLIDED WITH THE VISUAL APPROACH SLOPE INDICATOR (VASI). THE PILOT STATED THAT THE "X" ON THE RUNWAY MEANT THAT HE COULD NOT LAND ON THE RIGHT SIDE OF THE RUNWAY AND COULD HAVE LANDED THE LEFT SIDE. FEDERAL AVIATION REGULATIONS DEFINE AN "X" ON THE RUNWAY END TO MEAN THAT THE RUNWAY IS CLOSED AND IS NOT TO BE USED FOR TAKEOFFS OR LANDINGS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ANC82DAA09
- Event ID
- 20020917X02672
- Case number
- ANC82DAA09
- 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: 70e54a3525988918d463893e546c46cd0efe1743ce734516451ef3a1acb1702c; retrieved 2026-09-24T02:13:39.800Z.