20220619010669A

Accident · Substantial damage

FAA accident report · Cessna 172R · Owensboro, KY · June 19, 2022

Date
June 19, 2022 · 09:06 local
Place
Owensboro, KY
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N35491
NTSB investigation
NTSBERA22LA280
Reported as
Cessna 172R
Reported engine
Lycoming IO-360-L2A
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Student
Pilot’s flight hours
21 total21 in this make and model21 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.

This flight was the student pilot?s initial solo cross-country. He had received the required training and endorsements for the flight. The student received most of his flight training at an uncontrolled field and stated that he felt comfortable talking to ATC and that it did not cause extra stress. Upon arrival into owb, ATC had the pilot fly a straight in approach to runway 6 and report a three mile final. It was reported that the student and instructor discussed the possibility of a straight in approach, but had never actually practiced straight in approaches in the aircraft. The student reported that he began to configure for landing at approximately a four to five mile final. At a three mile final, the pilot called ATC and was cleared for the option. The pilot stated that his intent was to perform two touch and go?s followed by a full stop taxi back. On final, the pilot recalled being a little slow and a little high, using the VASI as reference, but felt the landing would still be safe. Upon touchdown, the pilot recalled the nose wheel touching first and the aircraft porpoised. The pilot reported adding back pressure as a response. It was reported that the aircraft skidded and the pilot overcompensated by applying too much rudder, causing the runway excursion.

As the FAA filed it

THIS FLIGHT WAS THE STUDENT PILOT?S INITIAL SOLO CROSS-COUNTRY. HE HAD RECEIVED THE REQUIRED TRAINING AND ENDORSEMENTS FOR THE FLIGHT. THE STUDENT RECEIVED MOST OF HIS FLIGHT TRAINING AT AN UNCONTROLLED FIELD AND STATED THAT HE FELT COMFORTABLE TALKING TO ATC AND THAT IT DID NOT CAUSE EXTRA STRESS. UPON ARRIVAL INTO OWB, ATC HAD THE PILOT FLY A STRAIGHT IN APPROACH TO RUNWAY 6 AND REPORT A THREE MILE FINAL. IT WAS REPORTED THAT THE STUDENT AND INSTRUCTOR DISCUSSED THE POSSIBILITY OF A STRAIGHT IN APPROACH, BUT HAD NEVER ACTUALLY PRACTICED STRAIGHT IN APPROACHES IN THE AIRCRAFT. THE STUDENT REPORTED THAT HE BEGAN TO CONFIGURE FOR LANDING AT APPROXIMATELY A FOUR TO FIVE MILE FINAL. AT A THREE MILE FINAL, THE PILOT CALLED ATC AND WAS CLEARED FOR THE OPTION. THE PILOT STATED THAT HIS INTENT WAS TO PERFORM TWO TOUCH AND GO?S FOLLOWED BY A FULL STOP TAXI BACK. ON FINAL, THE PILOT RECALLED BEING A LITTLE SLOW AND A LITTLE HIGH, USING THE VASI AS REFERENCE, BUT FELT THE LANDING WOULD STILL BE SAFE. UPON TOUCHDOWN, THE PILOT RECALLED THE NOSE WHEEL TOUCHING FIRST AND THE AIRCRAFT PORPOISED. THE PILOT REPORTED ADDING BACK PRESSURE AS A RESPONSE. IT WAS REPORTED THAT THE AIRCRAFT SKIDDED AND THE PILOT OVERCOMPENSATED BY APPLYING TOO MUCH RUDDER, CAUSING THE RUNWAY EXCURSION.

NTSB investigation

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

Other reports on N35491 · 1

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