20240426005369I

Incident · Minor damage

FAA incident report · Cessna 170A · Olympia, WA · April 26, 2024

Date
April 26, 2024 · 16:14 local
Place
Olympia, WA
Airport
Olympia Regional
Phase of flight
Landing: Rollout
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N60CH
Reported as
Cessna 170A
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Commercial pilot, flight instructor, private pilot
Pilot’s flight hours
3,672 total117 in this make and model35 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.

On April 26, 2024, a commercial-instructor pilot operated a tailwheel airplane as pilot-in-command while conducting flight instruction at Olympia airport in Olympia, Washington. The purpose of this flight was to train a new student pilot on flying and handling a tailwheel airplane. The pilot received a wind check from the Olympia control tower and verified it using the windsock, which appeared limp and did not indicate the wind direction or movement reported by the tower. Despite the discrepancy, the instructor allowed the student to proceed with the landing.

Upon touchdown, the aircraft continued straight down the runway, and the instructor praised the student for the near-perfect landing. However, a sudden gust of wind caused the tail to swing to the right, initiating a ground loop. The instructor managed to keep the aircraft on the runway, except for the left wheel, but the left wingtip touched the ground, causing minor wingtip damage. The aircraft came to a stop 180 degrees from its original direction.

The instructor informed the Olympia tower that a tug truck was needed, but after inspecting the aircraft, realized the damage was minimal and taxied the plane back to the hangar without assistance. The FAA learned of the incident on April 26, 2024, as reported by the airport manager. Contributing factors was attributed to the instructor's decision to land despite conflicting wind information from the tower and the windsock, and the failure to consider the crosswind component.

The instructor acknowledged that initially, there were no wind gusts, and previous landings had been uneventful. However, root cause analysis reveals decisions to continue landings with a possible high cross wind component could have been better mitigated. The pilot admitted that in hindsight, opting for a different runway or performing a go-around would have been safer. The instructor committed to establishing a wind speed cut-off for future training flights to avoid similar incidents.

The FAA inspector reviewed the incident and after speaking with the pilot and hearing what could have been conducted differently, possible favorable outcomes versus negative outcomes and the key lessons learned in this event, pilot has learned from this incident. Based on these facts and circumstances, a compliance action is required and appropriate. The FAA inspector was able to bring the pilot back into compliance. Items discussed included aeronautical decision-making skills and situational awareness. The pilot understands these items were discussed to regain compliance per the compliance program. The FAA inspector evaluated the pilots root cause analysis and corrective actions and concurs that they appear adequate to prevent similar events from occurring in the future. The lessons learned because of the experience and counseling has reestablished confidence in the pilots’ ability to operate in compliance and safely within the national airspace system. No further action or no follow-up is required or planned.

Finally, the FAA airworthiness inspector found that the privacy data omitted aircraft was not airworthy because of two missing placards which are required per the aircraft type design as operating limitations. The FAA inspector counseled the privacy data omitted on the required placards and put a FAA condition notice on the aircraft and instructed the privacy data omitted to mail the form back to him when the privacy data omitted had corrected the regulatory violation. This event is eligible for a compliance action. The root cause was the privacy data omitted was unaware of the required placards needed for his aircraft. This event has been closed. No further corrective action needed.

As the FAA filed it

ON APRIL 26, 2024, A COMMERCIAL-INSTRUCTOR PILOT OPERATED A TAILWHEEL AIRPLANE AS PILOT-IN-COMMAND WHILE CONDUCTING FLIGHT INSTRUCTION AT OLYMPIA AIRPORT IN OLYMPIA, WASHINGTON. THE PURPOSE OF THIS FLIGHT WAS TO TRAIN A NEW STUDENT PILOT ON FLYING AND HANDLING A TAILWHEEL AIRPLANE. THE PILOT RECEIVED A WIND CHECK FROM THE OLYMPIA CONTROL TOWER AND VERIFIED IT USING THE WINDSOCK, WHICH APPEARED LIMP AND DID NOT INDICATE THE WIND DIRECTION OR MOVEMENT REPORTED BY THE TOWER. DESPITE THE DISCREPANCY, THE INSTRUCTOR ALLOWED THE STUDENT TO PROCEED WITH THE LANDING.

UPON TOUCHDOWN, THE AIRCRAFT CONTINUED STRAIGHT DOWN THE RUNWAY, AND THE INSTRUCTOR PRAISED THE STUDENT FOR THE NEAR-PERFECT LANDING. HOWEVER, A SUDDEN GUST OF WIND CAUSED THE TAIL TO SWING TO THE RIGHT, INITIATING A GROUND LOOP. THE INSTRUCTOR MANAGED TO KEEP THE AIRCRAFT ON THE RUNWAY, EXCEPT FOR THE LEFT WHEEL, BUT THE LEFT WINGTIP TOUCHED THE GROUND, CAUSING MINOR WINGTIP DAMAGE. THE AIRCRAFT CAME TO A STOP 180 DEGREES FROM ITS ORIGINAL DIRECTION.

THE INSTRUCTOR INFORMED THE OLYMPIA TOWER THAT A TUG TRUCK WAS NEEDED, BUT AFTER INSPECTING THE AIRCRAFT, REALIZED THE DAMAGE WAS MINIMAL AND TAXIED THE PLANE BACK TO THE HANGAR WITHOUT ASSISTANCE. THE FAA LEARNED OF THE INCIDENT ON APRIL 26, 2024, AS REPORTED BY THE AIRPORT MANAGER. CONTRIBUTING FACTORS WAS ATTRIBUTED TO THE INSTRUCTOR'S DECISION TO LAND DESPITE CONFLICTING WIND INFORMATION FROM THE TOWER AND THE WINDSOCK, AND THE FAILURE TO CONSIDER THE CROSSWIND COMPONENT.

THE INSTRUCTOR ACKNOWLEDGED THAT INITIALLY, THERE WERE NO WIND GUSTS, AND PREVIOUS LANDINGS HAD BEEN UNEVENTFUL. HOWEVER, ROOT CAUSE ANALYSIS REVEALS DECISIONS TO CONTINUE LANDINGS WITH A POSSIBLE HIGH CROSS WIND COMPONENT COULD HAVE BEEN BETTER MITIGATED. THE PILOT ADMITTED THAT IN HINDSIGHT, OPTING FOR A DIFFERENT RUNWAY OR PERFORMING A GO-AROUND WOULD HAVE BEEN SAFER. THE INSTRUCTOR COMMITTED TO ESTABLISHING A WIND SPEED CUT-OFF FOR FUTURE TRAINING FLIGHTS TO AVOID SIMILAR INCIDENTS.

THE FAA INSPECTOR REVIEWED THE INCIDENT AND AFTER SPEAKING WITH THE PILOT AND HEARING WHAT COULD HAVE BEEN CONDUCTED DIFFERENTLY, POSSIBLE FAVORABLE OUTCOMES VERSUS NEGATIVE OUTCOMES AND THE KEY LESSONS LEARNED IN THIS EVENT, PILOT HAS LEARNED FROM THIS INCIDENT. BASED ON THESE FACTS AND CIRCUMSTANCES, A COMPLIANCE ACTION IS REQUIRED AND APPROPRIATE. THE FAA INSPECTOR WAS ABLE TO BRING THE PILOT BACK INTO COMPLIANCE. ITEMS DISCUSSED INCLUDED AERONAUTICAL DECISION-MAKING SKILLS AND SITUATIONAL AWARENESS. THE PILOT UNDERSTANDS THESE ITEMS WERE DISCUSSED TO REGAIN COMPLIANCE PER THE COMPLIANCE PROGRAM. THE FAA INSPECTOR EVALUATED THE PILOTS ROOT CAUSE ANALYSIS AND CORRECTIVE ACTIONS AND CONCURS THAT THEY APPEAR ADEQUATE TO PREVENT SIMILAR EVENTS FROM OCCURRING IN THE FUTURE. THE LESSONS LEARNED BECAUSE OF THE EXPERIENCE AND COUNSELING HAS REESTABLISHED CONFIDENCE IN THE PILOTS’ ABILITY TO OPERATE IN COMPLIANCE AND SAFELY WITHIN THE NATIONAL AIRSPACE SYSTEM. NO FURTHER ACTION OR NO FOLLOW-UP IS REQUIRED OR PLANNED.

FINALLY, THE FAA AIRWORTHINESS INSPECTOR FOUND THAT THE ^PRIVACY DATA OMITTED^ AIRCRAFT WAS NOT AIRWORTHY BECAUSE OF TWO MISSING PLACARDS WHICH ARE REQUIRED PER THE AIRCRAFT TYPE DESIGN AS OPERATING LIMITATIONS. THE FAA INSPECTOR COUNSELED THE ^PRIVACY DATA OMITTED^ ON THE REQUIRED PLACARDS AND PUT A FAA CONDITION NOTICE ON THE AIRCRAFT AND INSTRUCTED THE ^PRIVACY DATA OMITTED^ TO MAIL THE FORM BACK TO HIM WHEN THE ^PRIVACY DATA OMITTED^ HAD CORRECTED THE REGULATORY VIOLATION. THIS EVENT IS ELIGIBLE FOR A COMPLIANCE ACTION. THE ROOT CAUSE WAS THE ^PRIVACY DATA OMITTED^ WAS UNAWARE OF THE REQUIRED PLACARDS NEEDED FOR HIS AIRCRAFT. THIS EVENT HAS BEEN CLOSED. NO FURTHER CORRECTIVE ACTION NEEDED.