# Accident 20041119032189A: Cessna 172N, Lakeville, MN, November 19, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 19, 2004, 19:47 local time
- Place: Lakeville, MN
- Airport: Airlake Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 44.6278° N, 93.2281° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.6278&lon=-93.2281&mi=10
- Aircraft: N737CR, a cancelled registration (https://openairdocs.org/deregistered/N737CR-2013-09-30) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYC O360A4M
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 700 total, 400 in this make and model, 90 in the last 90 days
- NTSB investigation: [NTSB CHI05CA034](https://openairdocs.org/ntsb/CHI05CA034) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041119032189A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE PILOT ^PRIVACY^ FLEW THE ILS APPROACH INTO KLVN UNDER IFR CONDITIONS ON THE EVENING OF NOVEMBER 19, 2004. HE WAS FLYING N737CR A CESSNA 172 AT 120 KNOTS ON THE APPROACH. THE PILOT ^PRIVACY^ HAD TROUBLE SEEING THE RUNWAY ON THE APPROACH DUE TO THE LIGHTS ON LOW INTENSITY. THE LIGHTS AT LVN ARE PILOT CONTROLLED ON THE COMMON TRAFFIC ADVISORY FREQUENCY. WHEN THE PILOT ^PRIVACY^ BROKE OUT ON THE APPROACH APPROXIMATELY 500 FEET AGL HE WAS HIGH ON THE APPROACH AND FAST AND HAD TO MANEUVER TO CENTER WITH THE RUNWAY. THE PILOT ^PRIVACY^ LANDED ABOUT HALFWAY DOWN THE RUNWAY AND GOT ON THE BRAKES AFTER LANDING. THE PILOT ^PRIVACY^ WAS UNABLE TO KEEP THE AIRPLANE FROM HYDROPLANING DOWN THE RUNWAY AND OFF THE END. THE AIRPLANE ENDED UP ABOUT 600 FEET FROM THE END OF THE RUNWAY ON THE EMBANKMENT OF A CROSSING ROAD. THE NOSE WHEEL WAS BENT BACK A LITTLE AND MINOR PROP DAMAGE. IT CAVED IN PART OF THE FIREWALL OF THE AIRPLANE AND CONSTITUTES AN ACCIDENT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CHI05CA034](https://openairdocs.org/ntsb/CHI05CA034), Nov 20, 2004: Cessna 172N (N737CR), Lakeville, MN, substantial damage. Probable cause: The pilot misjudged his distance and speed which resulted in an overrun.. Factors were the wet runway, the grass and the berm.

## Other reports on N737CR (1)

Matched to the same aircraft by N-number and date.

- [Incident 20040817025599I](https://openairdocs.org/incident/20040817025599I), Aug 17, 2004: Cessna 172N (N737CR), Perry, FL. (-23) On August 17, 2004, at 0955 EST, a Cessna 172, registered to kurt roy, departed new port richey, Florida, for montgomery regional airport Alabama. The…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.