SEA05CA135 · Cessna 170B
Cessna 170B · Accident: loss of control on ground/water during landing
From Laurel Municipal Airport (6S8) to Laurel Municipal Airport (6S8)
Event
- NTSB case
- SEA05CA135
- 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
- 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
- N2619D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Laurel Municipal Airport (6S8), Laurel, MTTo Laurel Municipal Airport (6S8), Laurel, MT
- 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 · landing roll
- 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
- Loss of control on ground/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(cfi) › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the flight instructor, the purpose of the flight was to work on landings. After the student completed two landings on runway 22, the instructor suggested they switch to runway 04 "as the wind sock was showing some movement from the east." The instructor then made two landings on runway 04. During the landing roll of the second landing, she was discussing the landing with the student and looked over at him. The airplane "veered to the right into the grass," and the addition of power did not stop the airplane from ground looping. The left wing and left elevator contacted the ground and sustained structural damage.
Probable cause
The flight instructor's failure to maintain directional control during the landing roll, which resulted in an inadvertent ground loop. A contributing factor was the flight instructor's diverted attention to talking with the student.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05CA135
- Event ID
- 20050718X01042
- Case number
- SEA05CA135
- 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, coordinates. 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: 5d6d2ae30a2edb9eb934f4b0bbe008766fe6e0f8ceb181c4d16e2eb9843f0047; retrieved 2026-09-22T05:42:54.669Z.