# Accident 19981127032452A: Cessna 172M, Brainerd, MN, November 27, 1998 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: November 27, 1998 - Place: Brainerd, MN - Airport: Brainerd-Crow Wing Co -Walter - Damage: Substantial damage - Collision: Midair collision, second aircraft - Phase of flight: Level Off Touchdown - Operating rules: General operating rules (Part 91) - Location: 46.3491° N, 94.1905° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=46.3491&lon=-94.1905&mi=10 - Aircraft: N80357, a cancelled registration (https://openairdocs.org/deregistered/N80357-2014-11-19) (OpenAirDocs) - Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: CESSNA 172M - Fatal injuries: 0 - Pilot certificates: Student - NTSB investigation: [NTSB CHI99LA040](https://openairdocs.org/ntsb/CHI99LA040) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19981127032452A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ACFT WAS ON FINAL WHEN ANOTHER CESSNA LANDED ON TOP OF IT. (.19)NARRATIVE - SAME AS CHI99LAO40B(N80357) ON NOVEMBER 27, 1998, AT 1201N CENTRAL STANDARD TIME, A CESSNA 172P, N52502, PILOTED BY A PRIVATE PILOT, RECEIVED SUBATANTIAL DAMAGE IN COLLISION WITH A CESSNA 172M, N80357, DURING TOUCHDOWN ON RUNWAY 23 (6,500' X 150', ASPHALT/DRY) AT BRAINERD-CROW WING COUNTY REGIONAL AIRPORT NEAR BRAINERD, MINNESOTA. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE 14 CFR PART 91 PERSONAL FLIGHT WAS NOT OPERATING UNDER A PLIGHT PLAN. THE PILOT AND PASSENGER REPORTED MINOR INJURIES. THE FLIGHT ORIGINATED AT BARABOO WISCONSIN DELLS AIRPORT, NEAR BARABOO, WISCONSIN, AT 0930, AND WAS ENROUTE TO WILLMAR, MINNESOTA. THE PILOT OF N52505 REPORTED THAT HE WAS SIGHTSEEING OVER A LAKE LOCATED NORTH OF THE AIRPORT WHEN HE DECIDED TO LAND AT BRAINERD. THE PILOT STATED THAT HE HAD MADE A CALL ON THE COMMON TRAFFIC ADVISORY FREQUENCY (CTAF) OF 122.7 AND DID NOT HEAR ANY OTHER TRAFFIC IN THE AREA. HE THEN SELECTED THE AUTOMATED SURFACE OBSERVING SYSTEM (ASOS) FREQUENCY, OBTAINED THE BRAINERD WEATHER AND THEN RESELECTED THE BRAINERD CTAF. WHILE MAKING HIS STRAIGHT-IN APPRO ACH TO RUNWAY 23, THE PILOT STATED THAT HE DID NOT SEE ANY OTHER TRAFFIC AND ONLY RECALLS EXITING THE AIRPLANE AFTER THE COLLISION. THE PILOT STATED THAT THERE WERE PROPELLER MARKS ON THE TOP SIDE OF N80357. A WITNESS STATED THAT HE SAW N52502 OVERTAKE AND LAND ON TOP OF N80357, WHICH HAD COMPLETED ITS TOUCHDOWN ON RUNWAY 23. ## 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 CHI99LA040](https://openairdocs.org/ntsb/CHI99LA040), Nov 27, 1998: Cessna 172M (N80357), Brainerd, MN, substantial damage. Probable cause: The visual lookout not obtained/maintained by the pilot of the other aircraft. Contributing factors were the unicom frequency not selected and the traffic advisory not issued by the pilot of the… ## Other reports on N80357 (2) Matched to the same aircraft by N-number and date. - [Accident 19890822031489A](https://openairdocs.org/incident/19890822031489A), Aug 22, 1989: Cessna 172M (N80357), Clear Lake, MN, Substantial damage. Tried to land on a sod strip with only two lights at end of strip. Landed on side of strip in soft ground. Nosed over - [Incident 19830905065399I](https://openairdocs.org/incident/19830905065399I), Sep 5, 1983: Cessna 172M (N80357), Des Moines, IA. Ran out of fuel on final approach. Landed in a vacant lot. No pilot or medical certificate with him. 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.