OpenAirDocs.org

20041119032189A

Accident · Substantial damage
Open the Markdown

FAA accident report · Cessna 172N · Lakeville, MN · November 19, 2004

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
November 19, 2004 · 19:47 local
Place
Lakeville, MN
Airport
Airlake Airport
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N737CR
NTSB investigation
NTSBCHI05CA034
Reported as
Cessna 172N
Reported engine
Lycoming O360A4M
People aboard
1
Fatal injuries
0
Pilot’s flight hours
700 total400 in this make and model90 in the last 90 days
N737CRRegistration cancelled Sep 30, 2013 · Cessna 172NS/N 17269318 · Built 1977Airframe modelCessna 172NEngine modelLycoming 0-320 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) The pilot privacy data omitted 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 data omitted 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 data omitted 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 data omitted landed about halfway down the runway and got on the brakes after landing. The pilot privacy data omitted 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.

As the FAA filed it

(-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.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB CHI05CA034Accident · No injuriesData collectionFinal reportLakeville, MNThe pilot misjudged his distance and speed which resulted in an overrun.. Factors were the wet runway, the grass and the berm.Nov 20, 2004 · Substantial damage

Other reports on N737CR · 1

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

Incident 20040817025599INormal Cruise · 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 pilot kurt roy, became sick and had difficulty flying the aircraft. The pilot contacted ATC and…Aug 17, 2004