CHI02LA175 · Cessna 172N
Cessna 172N · Accident: on ground/water collision with object while taxiing
From Crystal Airport (MIC) to Crystal Airport (MIC)
Event
- NTSB case
- CHI02LA175
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N4808F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Crystal Airport (MIC), Minneapolis, MNTo Crystal Airport (MIC), Minneapolis, MN
- 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
- Taxi · from runway
- 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
- On ground/water 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 › Clearance, 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
The aircraft sustained substantial damage when it collided with a fuel truck while taxiing off the runway after landing. The pilot stated that a fuel truck was driving on the taxiway to the left side of the runway. The pilot stated she stopped on the runway and requested taxi instructions from the control tower. She stated that the control tower told her to exit the runway on to the taxiway where the fuel truck was located. The pilot reported that she again communicated with the control tower to clarify the situation and the tower stated that they did not want the aircraft stopped at the end of the runway. According to the pilot, the fuel truck moved off of the taxiway to the northeast side on the grass. She stated that when the aircraft passed the fuel truck the left wing struck an extension on the end of the truck.
Probable cause
The pilot did not maintain clearance from the vehicle while taxiing. A factor was the fuel truck.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02LA175
- Event ID
- 20020627X00981
- Case number
- CHI02LA175
- 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: 3ce29e577c276d7b027a044a0996b91adb314cf5e86b4d8a6d500973ae67a49c; retrieved 2026-09-22T10:49:10.103Z.