ERA12CA416 · Cessna 172M
CK Leasing Services Cessna 172M · Accident: ground collision during landing
From Harford County Airport (0W3) to Harford County Airport (0W3)
Event
- NTSB case
- ERA12CA416
- 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 172M
- 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
- N73134
- Operator
- CK Leasing Services
- Onboard fatalities
- Unknown
- Route
- From Harford County Airport (0W3), Churchville, MDTo Harford County Airport (0W3), Churchville, MD
- 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
- 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
- Ground collision
- 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
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was preparing to land at the airport and that he made radio calls on the common traffic advisory frequency (CTAF) to announce the airplane's position on the downwind, base, and final legs of the traffic pattern. While on the landing roll, as the airplane traveled over a crest in the runway, the pilot observed a tractor crossing the runway from left to right. The pilot steered the airplane to the right to avoid a collision, and the airplane's left wing contacted the tractor, which resulted in substantial damage. The operator of the tractor stated that he heard the airplane's CTAF transmissions but proceeded to cross the runway because he assumed that the airplane was already clear of the runway. The pilot reported there were no mechanical malfunctions or anomalies with the airplane.
Probable cause
The tractor operator's failure to confirm the landing airplane's position before entering an active runway, which resulted in a ground collision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12CA416
- Event ID
- 20120627X01450
- Case number
- ERA12CA416
- 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. 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: 27b70ef3cf12aeb4bdf6b5d15b215e7e44f7024dacaa50329a897f6bab91bf8b; retrieved 2026-09-15T18:38:29.843Z.