OpenAirDocs.org

20240211002819I

Incident · Minor damage
Open the Markdown

FAA incident report · Cessna 182S · Oxnard, CA · February 11, 2024

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
February 11, 2024 · 14:10 local
Place
Oxnard, CA
Airport
Oxnard Airport
Phase of flight
Landing: Approach
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N182TA
Reported as
Cessna 182S
Reported engine
Lycoming IO-540 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
600 total105 in this make and model25 in the last 90 days
N182TARegistered now · Cessna 182SS/N 18280062Airframe modelCessna 182SEngine modelLycoming IO-540 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.

The privacy data omitted of the aircraft in this incident, a non-current commercial pilot/cfi with his friend a current private pilot whom the privacy data omitted had taught during his initial flight training years prior, arrived at the airport for local pattern work. The friend agreed to be the PIC during the flight, but the privacy data omitted would take the controls during the pattern work too. After the PIC private pilot completed one pattern the privacy data omitted suggested the private pilot approach the runway slower and flare at a slower speed just before touchdown. On the second pattern the privacy data omittedtook the controls, and the private pilot allowed the privacy data omitted to get too low on approach. The aircraft hit some mals-f poles just before landing. Upon landing the nose gear collapsed allowing the prop to hit the runway as the aircraft came to rest. The damage was limited to nose gear collapsing, damage from the mals-f poles on the lower part of the fuselage and the prop hitting the runway when the nose gear collapsed. There were no injuries, and the aircraft was towed back to the hanger.

As the FAA filed it

THE ^PRIVACY DATA OMITTED^ OF THE AIRCRAFT IN THIS INCIDENT, A NON-CURRENT COMMERCIAL PILOT/CFI WITH HIS FRIEND A CURRENT PRIVATE PILOT WHOM THE ^PRIVACY DATA OMITTED^ HAD TAUGHT DURING HIS INITIAL FLIGHT TRAINING YEARS PRIOR, ARRIVED AT THE AIRPORT FOR LOCAL PATTERN WORK. THE FRIEND AGREED TO BE THE PIC DURING THE FLIGHT, BUT THE ^PRIVACY DATA OMITTED^ WOULD TAKE THE CONTROLS DURING THE PATTERN WORK TOO. AFTER THE PIC PRIVATE PILOT COMPLETED ONE PATTERN THE ^PRIVACY DATA OMITTED^ SUGGESTED THE PRIVATE PILOT APPROACH THE RUNWAY SLOWER AND FLARE AT A SLOWER SPEED JUST BEFORE TOUCHDOWN. ON THE SECOND PATTERN THE ^PRIVACY DATA OMITTED^TOOK THE CONTROLS, AND THE PRIVATE PILOT ALLOWED THE ^PRIVACY DATA OMITTED^ TO GET TOO LOW ON APPROACH. THE AIRCRAFT HIT SOME MALS-F POLES JUST BEFORE LANDING. UPON LANDING THE NOSE GEAR COLLAPSED ALLOWING THE PROP TO HIT THE RUNWAY AS THE AIRCRAFT CAME TO REST. THE DAMAGE WAS LIMITED TO NOSE GEAR COLLAPSING, DAMAGE FROM THE MALS-F POLES ON THE LOWER PART OF THE FUSELAGE AND THE PROP HITTING THE RUNWAY WHEN THE NOSE GEAR COLLAPSED. THERE WERE NO INJURIES, AND THE AIRCRAFT WAS TOWED BACK TO THE HANGER.