FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07CA001 · Cessna 180K

1 Oct 2006 · Barton City, MI, United States

Cessna 180K · Accident: overrun during landing

From Oakland County International Airport (PTK) to Barton City, MI (private airstrip)

Report a problem

Event

NTSB case
CHI07CA001
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 180K

Aircraft type
Cessna 180
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
N64257
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oakland County International Airport (PTK), Pontiac, MITo Barton City, MI (private airstrip)
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
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
Overrun
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 › Proper touchdown point, not attained
  • Pilot in command › Wrong runway, selected

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was substantially damaged when it overran the end of the runway on landing. The pilot reported that the intended destination was a private airstrip with an east-west oriented runway about 1,200 feet long, and a north-south oriented runway about 2,000 feet long. The pilot stated that when he overflew the windsock before landing, it appeared that winds were about 10 knots directly out of the north. He set up for a landing to the east; however, he "landed long" and subsequently "ran out of runway." The airplane encountered a rock pile located off the end of the runway. The pilot reported that upon exiting the airplane after the accident, he noticed that the wind was variable and appeared to have shifted. He commented that the wind might have gotten behind him on landing. Winds recorded at the Oscoda-Wurtsmith Airport (OSC), located about 16 nautical miles southeast of the accident site, at 1058, were from 280 degrees at 11 knots, gusting to 16 knots.

Probable cause

The pilot's failure to attain a proper touchdown point and his inadvertent selection of a downwind runway, which resulted in the overrun. A contributing factor was the tailwind encountered during landing. Additional factors were the wet, turf runway, and the rock pile located off the end of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07CA001
Event ID
20061106X01612
Case number
CHI07CA001
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: 9b3d1674b190a1b12abda7f8ccd4be498d0e7c282a2dcceb6442d84b242bbfc2; retrieved 2026-09-22T04:23:07.024Z.