OpenAirDocs.org

19981127032452A

Accident · Substantial damage
Open the Markdown

FAA accident report · Cessna 172M · Brainerd, MN · November 27, 1998

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
November 27, 1998
Place
Brainerd, MN
Airport
Brainerd-Crow Wing Co -Walter
Phase of flight
Level Off Touchdown
Operating rules
General operating rules (Part 91)
Collision
Midair collision, second aircraft
Damage
Substantial damage
Aircraft
N80357
NTSB investigation
NTSBCHI99LA040
Reported as
Cessna 172M
Fatal injuries
0
Pilot’s certificate
Student
N80357Registration cancelled Nov 19, 2014 · Cessna 172MS/N 17266546 · Built 1976Airframe modelCessna 172MEngine 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.

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.

As the FAA filed it

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.

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 CHI99LA040Accident · Minor injuriesLimited investigationFinal reportBrainerd, MNThe 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 aircraft. An additional factor was the aircraft moving on…Nov 27, 1998 · 2 aircraft · Substantial damage

Other reports on N80357 · 2

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

Accident 19890822031489ARoll-Out (Fixed Wing) · Clear Lake, MNTried to land on a sod strip with only two lights at end of strip. Landed on side of strip in soft ground. Nosed overAug 22, 1989 · Substantial damageIncident 19830905065399IFinal Approach · Des Moines, IARan out of fuel on final approach. Landed in a vacant lot. No pilot or medical certificate with him.Sep 5, 1983