37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 920841 |
Time | |
Date | 201011 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | SAEZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B727 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | SID TORUL 1 |
Flight Plan | IFR |
Component | |
Aircraft Component | Electronic Flt Bag (EFB) |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 55 Flight Crew Total 6300 Flight Crew Type 1889 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
After pushback departure runway was changed to runway 11. During the taxi to runway 11; new performance data was calculated; the electronic flight bag [efb] was reprogrammed; charts were sent to captain's efb display and both pilot navs were properly reset.after takeoff the aircraft was being flown by the captain with the flight director in use; with data being input from the GPS. The captain followed the flight director but it took him off the SID departure track. I had called the course alive and when going through the course; I stated to the captain that we should be tracking the radial outbound. We were both unsure why the flight director was not giving proper guidance. I realized at that point that I had not updated the SID in the GPS and we were being given directions for the SID for the old runway; but we had departed runway 11. I then tried to change the SID in the GPS; but the GPS would not cross fill to the captains GPS unit. I then requested direct to urino; with the intentions of giving the captain a heading to fly from my GPS unit until able to get his to accept the change of input; but ATC told us to maintain the departure. The captain then continued off course as I repeated that we needed to turn left to re-intercept the departure track; but he failed to do so. ATC then told us that we were not flying the SID; to which I responded that we were turning left to re-intercept and that we were having navigation problems. At that point the captain turned left to re-intercept and shortly after ATC granted our request for direct urino; which we complied with. Other traffic was not a factor in the occurrence.the electronic flight bag that we were using was recently installed in our aircraft type and had caused a change in my habit pattern; causing me to not change the SID for our new takeoff runway. This was the main contributing factor. Another contributing factor is that the 727 has several non integrated systems (dual efb; dual GPS; performance data computer) that increase workload during runway changes. Other contributing factors; was the GPS failure to properly cross fill which would have allowed us to correct our mistake before leaving the SID and our failure to properly rebrief the new SID due to runway change.
Original NASA ASRS Text
Title: While flying a SID from SAEZ in a B727 equipped with after-market non-integrated dual EFBs; dual GPS and a Performance Data Computer; the flight crew was unable to recover from their failure to properly program a departure runway change given after pushback and a track deviation ensued. An ATC vector and clearance direct to an enroute fix allowed the flight crew to recover.
Narrative: After pushback departure runway was changed to Runway 11. During the taxi to Runway 11; new performance data was calculated; the electronic flight bag [EFB] was reprogrammed; charts were sent to Captain's EFB display and both pilot navs were properly reset.After takeoff the aircraft was being flown by the Captain with the flight director in use; with data being input from the GPS. The Captain followed the Flight director but it took him off the SID departure track. I had called the course alive and when going through the course; I stated to the Captain that we should be tracking the radial outbound. We were both unsure why the flight director was not giving proper guidance. I realized at that point that I had not updated the SID in the GPS and we were being given directions for the SID for the old runway; but we had departed Runway 11. I then tried to change the SID in the GPS; but the GPS would not cross fill to the Captains GPS unit. I then requested direct to URINO; with the intentions of giving the Captain a heading to fly from my GPS unit until able to get his to accept the change of input; but ATC told us to maintain the departure. The Captain then continued off course as I repeated that we needed to turn left to re-intercept the departure track; but he failed to do so. ATC then told us that we were not flying the SID; to which I responded that we were turning left to re-intercept and that we were having NAV problems. At that point the Captain turned left to re-intercept and shortly after ATC granted our request for direct URINO; which we complied with. Other traffic was not a factor in the occurrence.The electronic flight bag that we were using was recently installed in our aircraft type and had caused a change in my habit pattern; causing me to not change the SID for our new takeoff runway. This was the main contributing factor. Another contributing factor is that the 727 has several non integrated systems (Dual EFB; Dual GPS; Performance Data computer) that increase workload during runway changes. Other contributing factors; was the GPS failure to properly cross fill which would have allowed us to correct our mistake before leaving the SID and our failure to properly rebrief the new SID due to runway change.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.