A B737-300 ON TKOF RECEIVED 2 UNCOMMANDED RUDDER INPUTS. ONE AT 80 KTS AND THE SECOND AT ROTATION. FLT DATA RECORDER NOTED 80 KTS INPUT.

2003-04 · NASA ASRS report 579284

Date: 2003-04 · Aircraft: B737-300 · Phase: takeoff

Anomalies: aircraft-equipment-problem-critical|other-rudder-pedal-kick

Synopsis

A B737-300 ON TKOF RECEIVED 2 UNCOMMANDED RUDDER INPUTS. ONE AT 80 KTS AND THE SECOND AT ROTATION. FLT DATA RECORDER NOTED 80 KTS INPUT.

Narrative

ON TKOF RWY 8 AT ZZZ (WINDS 130 DEGS/10 KTS) WE RECEIVED A GUST LIKE MVR (R TO L) AT 80 KTS; THEN AGAIN AT ROTATION ANOTHER MORE AGGRESSIVE UNCOMMANDED RUDDER PEDAL INPUT REQUIRING PLT ACTION TO MAINTAIN CTL. THE SECOND EVENT; IN THE OPINION OF BOTH PLTS WAS MECHANICAL RATHER THAN ENVIRONMENTAL. AFTER PASSING FL180 THE CAPT (PNF) INITIATED A VOICE PATCH TO MAINT CTLR THROUGH DISPATCH. AFTER A LENGTHY DISCUSSION; DESCRIBING THE EVENT TO MAINT CTLR; IN MAINT CTLR'S OPINION THE EVENT WAS ENVIRONMENTALLY TRIGGERED AND NOT A MECHANICAL ISSUE. MAINT CTLR STATED THERE WAS NO FURTHER ACTION REQUIRED. THE CAPT QUERIED MAINT CTLR AS TO WHETHER OR NOT AN ENGINEERING WRITE-UP SHOULD BE MADE SO AS TO ALERT THE FOLLOW-ON CREW THAT SOMETHING UNUSUAL HAD TAKEN PLACE DURING TKOF. MAINT CTLR SAID 'NO; WRITE-UP FOR GUSTY WINDS ON TKOF WAS NOT REQUIRED.' FURTHER DISCUSSION BY MYSELF AND THE CAPT CONCERNING ALL POSSIBLE CONTRIBUTORS; IE; WIND GUST; FOREIGN OBJECT DAMAGE; TIRE CONDITIONS; AS WELL AS MAIN AND NOSE GEAR ASSEMBLIES; LED US TO THE DECISION THAT EVEN THOUGH WE WERE NOT CONCERNED ABOUT THE SAFETY OF THE FLT; WE WANTED TO DOCUMENT THE EVENT FOR THE NEXT FLT CREW THAT WAS TO ACCEPT THE ACFT. THE CAPT THEN INITIATED ANOTHER PHONE PATCH TO ACR X DISPATCH TO INFORM THAT WE WOULD WRITE UP THE EVENT UPON LNDG AND THAT THE ACFT WOULD REQUIRE A MAINT INSPECTION PRIOR TO THE NEXT FLT. AS A PRECAUTION THE CAPT ADVISED THE FLT ATTENDANTS OF THE INCIDENT AND ASKED THE PURSER TO INFORM THE OTHER FLT ATTENDANTS COMPLETING A 'CABIN ADVISORY.' WE FURTHER INFORMED ATC THAT WE WOULD LIKE THE EMER VEHICLES STANDING BY UPON LNDG AT ZZZ1 IN THE EVENT OF ANY UNUSUAL OCCURRENCE. NO EMER WAS DECLARED. LNDG WAS UNEVENTFUL ON RWY 12R IN ZZZ1. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED NO FINAL CONCLUSION HAS BEEN MADE AS TO THE CAUSE OF THE RUDDER INPUTS. THE RPTR SAID THE FLT DATA RECORDER DID RECORD THE 80 KT INCIDENT.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.