19970406004959A

Accident · Substantial damage

FAA accident report · Cessna 172K · Olathe, KS · April 6, 1997

Date
April 6, 1997 · 14:17 local
Place
Olathe, KS
Airport
Johnson County Executive Airport
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N46311
NTSB investigation
NTSBCHI97LA100
Reported as
Cessna 172K
Reported engine
Lycoming O320*
Fatal injuries
0
Pilot’s flight hours
181 total147 in this make and model10 in the last 90 days

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.

Lost control and flipped over landing in gusty crosswind. Exceeded aircrafts cross wind component. (.4)during the landing approach the pilot told ATC that the surface winds were '...near the recommended maximum for my plane... .' He said he told the controller he could divert to an airport which he specified. The pilot said the controller told him the winds at the airport he specified were worse. The pilot continued the landing. According to the pilot, the airplane was '...immediately pushed to the right by a gust... .' The airplane crossed runway 36 onto loping terrain where the airplane nosed over.' The winds were from 290 degrees at 19 knots gusting to 31 knots. An airport about 13 miles west of the accident airport had an east-west runway. The pilot said he didn't use that airport because he thought the same wind conditions existed there as the airport he had asked the controller about. The crosswind component for the airplane is 15 miles per hour (mph). The existing crosswind component during the landing was 18 knots (22 mph). (-23)pilot attempted a landing on runway 36 with reported winds of 29019G31 . Aircraft flipped over following a loss of control.

As the FAA filed it

LOST CONTROL AND FLIPPED OVER LANDING IN GUSTY CROSSWIND. EXCEEDED AIRCRAFTS CROSS WIND COMPONENT. (.4)DURING THE LANDING APPROACH THE PILOT TOLD ATC THAT THE SURFACE WINDS WERE '...NEAR THE RECOMMENDED MAXIMUM FOR MY PLANE... .' HE SAID HE TOLD THE CONTROLLER HE COULD DIVERT TO AN AIRPORT WHICH HE SPECIFIED. THE PILOT SAID THE CONTROLLER TOLD HIM THE WINDS AT THE AIRPORT HE SPECIFIED WERE WORSE. THE PILOT CONTINUED THE LANDING. ACCORDING TO THE PILOT, THE AIRPLANE WAS '...IMMEDIATELY PUSHED TO THE RIGHT BY A GUST... .' THE AIRPLANE CROSSED RUNWAY 36 ONTO LOPING TERRAIN WHERE THE AIRPLANE NOSED OVER.' THE WINDS WERE FROM 290 DEGREES AT 19 KNOTS GUSTING TO 31 KNOTS. AN AIRPORT ABOUT 13 MILES WEST OF THE ACCIDENT AIRPORT HAD AN EAST-WEST RUNWAY. THE PILOT SAID HE DIDN'T USE THAT AIRPORT BECAUSE HE THOUGHT THE SAME WIND CONDITIONS EXISTED THERE AS THE AIRPORT HE HAD ASKED THE CONTROLLER ABOUT. THE CROSSWIND COMPONENT FOR THE AIRPLANE IS 15 MILES PER HOUR (MPH). THE EXISTING CROSSWIND COMPONENT DURING THE LANDING WAS 18 KNOTS (22 MPH). (-23)PILOT ATTEMPTED A LANDING ON RUNWAY 36 WITH REPORTED WINDS OF 29019G31 . AIRCRAFT FLIPPED OVER FOLLOWING A LOSS OF CONTROL.

NTSB investigation

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