CHI07CA200 · Piper PA-28-181
Piper PA-28-181 · Accident: on ground/water collision with object during landing
From Lake Lawn Airport (C59) to Lake in the Hills Airport (3CK)
Event
- NTSB case
- CHI07CA200
- 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
Piper PA-28-181
- Aircraft type
- Piper PA-28
- 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
- N4419F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Lawn Airport (C59), Delavan, WITo Lake in the Hills Airport (3CK), Lake in the Hills, IL
- 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
- 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 › Aborted landing, delayed
- Pilot in command › Proper touchdown point, not attained
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 landed long and subsequently impacted a chain link airport perimeter fence and trees during an aborted landing on runway 26 (3,058 feet by 50 feet, asphalt). The pilot added full power, and near the end of the runway he pitched up, the airplane porpoised two or three times, and veered to the left of the runway. The airplane then pitched down and continued down the grassy slope left of the runway, where it subsequently impacted a chain link perimeter fence and trees. No mechanical anomalies with the airplane were reported by the pilot. The pilot stated in his accident report that the accident could have been prevented by performing a go-around.
Probable cause
The pilot's failure to achieve a proper touchdown point and delayed decision to abort the landing. Factors contributing to the accident include the chain link fence and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA200
- Event ID
- 20070726X01021
- Case number
- CHI07CA200
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-07-07.
- API snapshot SHA-256: 202e38682e9a37af50b1ceeb87f9d3b59617a35243bd7a7d48291f9c6bb71619; retrieved 2026-09-22T03:41:04.131Z.