NYC03LA144 · Cessna 170A
Cessna 170A · Accident: in flight collision with object during landing
From Richard Downing Airport (I40) to No airport
Event
- NTSB case
- NYC03LA144
- 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 170A
- 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
- N9067A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Richard Downing Airport (I40), Coshocton, OHTo No airport
- 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 · aborted
- 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 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 › Go-around, delayed
- Pilot in command › Proper touchdown point, not obtained
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 was landing to the north on a 1,200-foot-long, 30-foot-wide, turf runway. The runway contained a 300-foot-long flat touchdown area, followed by an incline of about 30-percent. The airplane touched down halfway down the runway and bounced. The pilot initiated a go-around; however, as the airplane climbed, the pilot observed two hay bales located about 30 feet beyond the end of the runway. He tried to avoid the hay bales by making a quick right turn, but the left side of the horizontal stabilizer hit the top of one of the bales. The airplane then pitched down and struck the ground nose first. The pilot did not over fly the field prior to the landing attempt, and was not aware of the hay bales until the airplane reached the crest of the runway.
Probable cause
The pilot's failure to obtain the proper touchdown point and delayed go-around. Factors in this accident were the up sloping runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03LA144
- Event ID
- 20030701X00996
- Case number
- NYC03LA144
- 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: ad3969169c0c8aa66656814d8f129ac7ce8aa7adbc9c3d7f40d270f0710585ce; retrieved 2026-09-21T19:26:15.000Z.