ANC25LA070 · Cessna 170B
Cessna 170B · Accident: loss of control on ground during landing
Event
- NTSB case
- ANC25LA070
- 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
- Event fatalities
- Unknown
- 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
- 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 170B
- Aircraft type
- Cessna 170
- 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
- N2694D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 73 years (built 1952)
- 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 · landing roll
- 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
- Loss of control on ground
- 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
- Aircraft › Aircraft oper/perf/capability
- 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 reported that, while landing in a tailwheel-equipped airplane, the airplane’s upwind tire touched the runway, and a gust of wind lifted the wing; the pilot attempted to correct with opposite aileron. Subsequently, the airplane turned to the right and the left wing contacted the ground, which resulted in substantial damage to the left wing. The pilot reported selecting runway 22 for landing. He reported the winds to be from 120° at 11 kts, gusting 18 kts. On previous flights, the pilot would land on the gravel area adjacent to the asphalt runway during crosswind conditions; however, prior to the accident flight, he was advised that landing on this area was no longer authorized. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during landing, which resulted in a ground loop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC25LA070
- Event ID
- 20250710200502
- Case number
- ANC25LA070
- 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: 023a46ce03db8146661f5e4b3df4f9f0d990a4164856d8d6efd96905fc26f210; retrieved 2026-09-16T20:04:05.993Z.