ANC86FA130 · Cessna 177RG
Cessna 177RG · Accident: in flight collision with terrain/water en route
From Homer Airport (HOM) to Merle K (Mudhole) Smith Airport (CDV)
Event
- NTSB case
- ANC86FA130
- 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
- 3 · 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
- Instrument Meteorological Cond
Cessna 177RG
- Aircraft type
- Cessna 177
- 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
- N52137
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Homer Airport (HOM), Homer, AKTo Merle K (Mudhole) Smith Airport (CDV), Cordova, 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
- En route · descent
- 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 terrain/water
- 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 › IFR procedure, not followed
- Pilot in command › Proper altitude, not maintained
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
AT 1323 ADT, THE PLT RPRTD NEAR HINCHINBROOK ISLAND & REQUESTED CLEARANCE FOR AN NDB-A APCH TO THE CORDOVA MILE 13 ARPT. ABOUT 3 MIN LATER, CORDOVA FSS PROVIDED CLEARANCE FOR THE APCH 'FROM OVER HINCHINBROOK.' RADAR DATA SHOWED THAT THE ACFT FLEW TO THE JOHNSTONE POINT (JOH) VOR, THEN BEGAN TRACKING ON A SSE HEADING TOWARD THE SUBSEQUENT ACCIDENT SITE. THE ACFT IMPACTED NEAR THE TOP OF A MTN AT AN ELEV OF ABOUT 2000 FT, APRX 10 MI SSE OF THE JOH VOR. FOR THE JOH TRANSITION (TO THE NDB-A APCH), THE PLT SHOULD HAVE TRACKED OUTBOUND FROM THE VOR FOR 15.5 MI ON A HEADING OF 083 DEG, WITH A MIN ALT OF 4000 FT, TO THE HINCHINBROOK INITIAL APCH FIX (IAP).
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ANC86FA130
- Event ID
- 20001213X34353
- Case number
- ANC86FA130
- 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: 4f05cbe0a60af1e07de973bb52f8df1e6b7271d73aa9e5319057ab44aad9454e; retrieved 2026-09-21T04:26:15.932Z.