37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 696496 |
Time | |
Date | 200605 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : sky.vor |
State Reference | OH |
Altitude | msl single value : 16000 |
Environment | |
Flight Conditions | IMC |
Weather Elements | Turbulence Rain |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zob.artcc |
Operator | common carrier : air carrier |
Make Model Name | B727 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 56 flight time total : 4587 flight time type : 3630 |
ASRS Report | 6964986 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : second officer |
Experience | flight time last 90 days : 8 flight time total : 2200 flight time type : 75 |
ASRS Report | 696495 |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : clearance other spatial deviation |
Independent Detector | other controllerb |
Resolutory Action | controller : issued advisory flight crew : returned to intended or assigned course |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance Aircraft |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Flight sdf cle ord. On the second leg cle to ord we were given a clearance cle sky crl J34 alphe pmm arrival to ord. 5 mins prior; we taxied to runway 24R. Tower told us to contact clearance on 125.05 for a rerte. Clearance gave us a new routing cle sky vwv VWV248 OXI095 spann OXI3 arrival to ord and to contact the tower. Tower cleared us for takeoff runway 24R. Things were getting rushed to make the wheels up time. I told the tower we were unable; that we need a few more mins while I reprogrammed the GPS. I thought this to be prudent to reprogram the GPS. I thought this to be prudent to reprogram the GPS prior to departure because we were departing into known WX and turbulence. The tower said they would have to call chicago and get us a new release time. Just as I put the last waypoint into the GPS; the tower called us and said that we were released and cleared for takeoff. I looked down at both GPS's as we taxied onto runway 24R and they both had sky as the takeoff waypoint. Everything looked good; but I had let myself become distraction by the radio call and had never xferred the new flight plan to the captain's GPS. His GPS still had the original flight plan with sky as the takeoff waypoint. If it would have been earlier in our duty period; I may have not been distraction by the tower radio transmission and have completed the task at hand. As departure vectored us around to sky VOR; they cleared us direct to sky VOR. The captain selected direct sky and entered it in his GPS then xferred it to my GPS; as he should have. When he did this; it dropped the new flight plan from my GPS and loaded the old flight plan from his GPS. Upon reaching sky VOR my GPS directed me to turn right. As I crossed the VOR; crl became the takeoff waypoint. We knew this was not right -- it should have been vwv. The captain started to reprogram the GPS when center asked us if we had a new flight plan. The captain told them we had not gotten another flight plan. Center then turned us to a heading of 270 degrees toward vwv and gave us the routing over oxi again. After a while center called and asked us to contact ZOB on the telephone; that there was a possible pilot deviation. Supplemental information from acn 696495: I think fatigue was a factor in that it decreased the workload capacity of the entire crew; first in not checking that the route was sent to the captain's FMC correctly; and subsequently in recognizing the old route was still in the FMC as we approached the first fix. As a so; I think I received adequate training in monitoring aircraft parameters such as leveloffs; final approach segments; and approach criteria to effectively monitor a final approach and landing; and en route leveloffs. This instance stresses to me the importance of monitoring flight parameters and changes to the FMC routing. I humbly recommend training for so's also include tools to monitor FMC changes; specifically when the route changes need to be pushed from one pilot's FMC to the other. In the future; I will most certainly monitor the FMC/GPS xfers; and ensure both pilots agree to the routing that is loaded.
Original NASA ASRS Text
Title: B727 UPGRADED TO GPS-FMS OP HAS A TRACK DEV WHEN AMENDED RTE IS LOADED IN ONLY THE #2 UNIT.
Narrative: FLT SDF CLE ORD. ON THE SECOND LEG CLE TO ORD WE WERE GIVEN A CLRNC CLE SKY CRL J34 ALPHE PMM ARR TO ORD. 5 MINS PRIOR; WE TAXIED TO RWY 24R. TWR TOLD US TO CONTACT CLRNC ON 125.05 FOR A RERTE. CLRNC GAVE US A NEW ROUTING CLE SKY VWV VWV248 OXI095 SPANN OXI3 ARR TO ORD AND TO CONTACT THE TWR. TWR CLRED US FOR TKOF RWY 24R. THINGS WERE GETTING RUSHED TO MAKE THE WHEELS UP TIME. I TOLD THE TWR WE WERE UNABLE; THAT WE NEED A FEW MORE MINS WHILE I REPROGRAMMED THE GPS. I THOUGHT THIS TO BE PRUDENT TO REPROGRAM THE GPS. I THOUGHT THIS TO BE PRUDENT TO REPROGRAM THE GPS PRIOR TO DEP BECAUSE WE WERE DEPARTING INTO KNOWN WX AND TURB. THE TWR SAID THEY WOULD HAVE TO CALL CHICAGO AND GET US A NEW RELEASE TIME. JUST AS I PUT THE LAST WAYPOINT INTO THE GPS; THE TWR CALLED US AND SAID THAT WE WERE RELEASED AND CLRED FOR TKOF. I LOOKED DOWN AT BOTH GPS'S AS WE TAXIED ONTO RWY 24R AND THEY BOTH HAD SKY AS THE TKOF WAYPOINT. EVERYTHING LOOKED GOOD; BUT I HAD LET MYSELF BECOME DISTR BY THE RADIO CALL AND HAD NEVER XFERRED THE NEW FLT PLAN TO THE CAPT'S GPS. HIS GPS STILL HAD THE ORIGINAL FLT PLAN WITH SKY AS THE TKOF WAYPOINT. IF IT WOULD HAVE BEEN EARLIER IN OUR DUTY PERIOD; I MAY HAVE NOT BEEN DISTR BY THE TWR RADIO XMISSION AND HAVE COMPLETED THE TASK AT HAND. AS DEP VECTORED US AROUND TO SKY VOR; THEY CLRED US DIRECT TO SKY VOR. THE CAPT SELECTED DIRECT SKY AND ENTERED IT IN HIS GPS THEN XFERRED IT TO MY GPS; AS HE SHOULD HAVE. WHEN HE DID THIS; IT DROPPED THE NEW FLT PLAN FROM MY GPS AND LOADED THE OLD FLT PLAN FROM HIS GPS. UPON REACHING SKY VOR MY GPS DIRECTED ME TO TURN R. AS I CROSSED THE VOR; CRL BECAME THE TKOF WAYPOINT. WE KNEW THIS WAS NOT RIGHT -- IT SHOULD HAVE BEEN VWV. THE CAPT STARTED TO REPROGRAM THE GPS WHEN CTR ASKED US IF WE HAD A NEW FLT PLAN. THE CAPT TOLD THEM WE HAD NOT GOTTEN ANOTHER FLT PLAN. CTR THEN TURNED US TO A HDG OF 270 DEGS TOWARD VWV AND GAVE US THE ROUTING OVER OXI AGAIN. AFTER A WHILE CTR CALLED AND ASKED US TO CONTACT ZOB ON THE TELEPHONE; THAT THERE WAS A POSSIBLE PLTDEV. SUPPLEMENTAL INFO FROM ACN 696495: I THINK FATIGUE WAS A FACTOR IN THAT IT DECREASED THE WORKLOAD CAPACITY OF THE ENTIRE CREW; FIRST IN NOT CHKING THAT THE RTE WAS SENT TO THE CAPT'S FMC CORRECTLY; AND SUBSEQUENTLY IN RECOGNIZING THE OLD RTE WAS STILL IN THE FMC AS WE APCHED THE FIRST FIX. AS A SO; I THINK I RECEIVED ADEQUATE TRAINING IN MONITORING ACFT PARAMETERS SUCH AS LEVELOFFS; FINAL APCH SEGMENTS; AND APCH CRITERIA TO EFFECTIVELY MONITOR A FINAL APCH AND LNDG; AND ENRTE LEVELOFFS. THIS INSTANCE STRESSES TO ME THE IMPORTANCE OF MONITORING FLT PARAMETERS AND CHANGES TO THE FMC ROUTING. I HUMBLY RECOMMEND TRAINING FOR SO'S ALSO INCLUDE TOOLS TO MONITOR FMC CHANGES; SPECIFICALLY WHEN THE RTE CHANGES NEED TO BE PUSHED FROM ONE PLT'S FMC TO THE OTHER. IN THE FUTURE; I WILL MOST CERTAINLY MONITOR THE FMC/GPS XFERS; AND ENSURE BOTH PLTS AGREE TO THE ROUTING THAT IS LOADED.
Data retrieved from NASA's ASRS site as of January 2009 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.