|
| Title: | Uncommanded yaw on takeoff, Boeing 737-73V, G-EZJR |
| Micro summary: | This Boeing 737-73V experienced an uncommanded transient yawing moment on takeoff. |
| Event Time: | 2003-04-08 at 1430 UTC |
| File Name: | 2003-04-08-UK.pdf |
| Publishing Agency: | Aircraft Accident Investigation Board (AAIB) |
| Publishing Country: | United Kingdom |
| Report number: | EW/C2003/04/02 |
| Pages: | 4 |
| Diversion Airport: | London Luton Airport, London, England |
| Site of event: | Takeoff, Luton |
| Departure: | London Luton Airport, London, England |
| Destination: | Vaasa Airport, Vaasa, Finland |
| Airplane Type(s): | Boeing 737-73V |
| Flight Phase: | Takeoff |
| Registration(s): | G-EZJR |
| Operator(s): | EasyJet |
| Type of flight: | Revenue |
| Occupants: | 124 |
| Fatalities: | 0 |
| Serious Injuries: | 0 |
| Minor/Non-Injured: | 124 |
| Other Injuries: | 0 |
| Diverted to: | London Luton Airport, London, England |
| Executive Summary: | Runway 08 was in use and whilst taxiing from the apron the pilots completed the flight control checks in accordance with company procedures. These involved the commander displacing the rudder pedals to full deflection in both directions whilst the co-pilot followed through on his own pedals, both pilots checking for full and free movement. The co-pilot then displaced the control wheel and control column in both directions, again to check for full and free movement. These control checks were completed without problem. After an uneventful taxi to the runway the aircraft was cleared to enter, backtrack and line up onRunway 08; it was then cleared for takeoff. The take-off run was normal until the commander raised the nosewheel off the ground during rotation when the crew stated that the aircraft suddenly jolted to one side, although they could not remember which way. The aircraft rapidly became airborne and the commander continued with the departure as the aircraft appeared to be handling perfectly normally once more. Once the after take-off checks were complete, the two pilots discussed the jolt and consulted the aircraft’s checklist. However, as the aircraft was now apparently operating perfectly normally, the checklist did not contain any relevant drill for them to follow. Finally, the commander contacted the Senior Cabin Crew Member (SCCM) who informed him that from the cabin, the jolt had been sufficiently severe to lead the SCCM to believe that the aircraft was about to deviate off the runway. Unable to find a cause for the disturbance during takeoff, but believing they had experienced some sort of uncommanded rudder event, the commander spoke with the company operations staff by radio. They in turn contacted the engineering department who advised that the aircraft should return to Luton for inspection. The aircraft was levelled at FL330 and given radar vectors to return to Luton. The commander briefed for the approach and landing and both pilots revised the immediate action items for an uncommanded rudder input in case they experienced another disturbance. The commander stated that he also added an additional 10 kt to the approach speed to give an increased margin of control. Having done this, the flight crew carried out a normal landing back at Luton and taxied to a stand where the aircraft was shut down. |
| Learning Keywords: | Operations - Upset - Uncommanded or excessive Yaw |
Accident Reports on DVD, Copyright © 2006 by Flight Simulation Systems, LLC. All Rights Reserved. All referenced trademarks are the property of their respective owners.www.fss.aero