 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 first officer report on a heading track deviation after failing to enter the correct transition into the FMC when departure las, nv.
| Attributes | |
| ACN | 535266 |
| Time | |
| Date | 200201 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : las.airport |
| State Reference | NV |
| Altitude | msl single value : 37000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zab.artcc tower : zzz.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Route In Use | departure sid : wyldd1.wyldd |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : multi engine pilot : instrument |
| Experience | flight time last 90 days : 200 flight time total : 6000 flight time type : 800 |
| ASRS Report | 535266 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | non adherence : company policies non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory |
| Consequence | faa : reviewed incident with flight crew other |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Chart Or Publication Environmental Factor |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
On the 4TH leg of my last day of 5 days straight, I got an RNAV clearance (wild 1) for my leg from las. I check or circle items on the sheet as they are read to me. In this case, I checked inw transition, which was in parenthesis next to the normal pgs transition. I had already entered the route of flight into the FMC. I then verified the data against the release seeing that was familiar, yet failing to change the transition. After the before start checklist, as normal, I stated the SID, altitude and special, failing to note the transition. At cruise altitude, a few mins after the airplane turned toward pgs, center asked us what our transition was. I then saw the check and realized the mistake. Center gave us a vector, and said it was no problem. It seems they are more vigilant while we're flying the new sids and stars. I have no excuse for allowing my complacency to cause this error and will not allow this 'gotcha' to 'get me' again. Not excuses, but requested possible factors are offered below: during my first 3 RNAV departures/arrs (on this pairing), we were vectored off and did not fly RNAV for very long. I may have (subconsciously) thought we'd be on a more direct clearance by then and not be RNAV-ing. Still no excuse though. The speed and routine nature of my routines contributed to my complacency. Very often we hear 'cleared as filed.' working 11 out of 16 days -- 5 on, 2 off, 5 on, with 1 commute. Recommendations: flying RNAV arrs/departures decreases dialogue between pilots and controllers. Dialogue that we are used to enables minor errors or misunderstanding to be more quickly resolved before they become gross errors. Therefore have a complete understanding of where you told the aircraft to go via the departure/arrival. Go to a pace commensurate with conditions. Speed should not be favored over accuracy, especially towards the end of a trip. Work smarter, not harder.
Original NASA ASRS Text
Title: A B737 FO RPT ON A HDG TRACK DEV AFTER FAILING TO ENTER THE CORRECT TRANSITION INTO THE FMC WHEN DEP LAS, NV.
Narrative: ON THE 4TH LEG OF MY LAST DAY OF 5 DAYS STRAIGHT, I GOT AN RNAV CLRNC (WILD 1) FOR MY LEG FROM LAS. I CHK OR CIRCLE ITEMS ON THE SHEET AS THEY ARE READ TO ME. IN THIS CASE, I CHKED INW TRANSITION, WHICH WAS IN PARENTHESIS NEXT TO THE NORMAL PGS TRANSITION. I HAD ALREADY ENTERED THE RTE OF FLT INTO THE FMC. I THEN VERIFIED THE DATA AGAINST THE RELEASE SEEING THAT WAS FAMILIAR, YET FAILING TO CHANGE THE TRANSITION. AFTER THE BEFORE START CHKLIST, AS NORMAL, I STATED THE SID, ALT AND SPECIAL, FAILING TO NOTE THE TRANSITION. AT CRUISE ALT, A FEW MINS AFTER THE AIRPLANE TURNED TOWARD PGS, CTR ASKED US WHAT OUR TRANSITION WAS. I THEN SAW THE CHK AND REALIZED THE MISTAKE. CTR GAVE US A VECTOR, AND SAID IT WAS NO PROB. IT SEEMS THEY ARE MORE VIGILANT WHILE WE'RE FLYING THE NEW SIDS AND STARS. I HAVE NO EXCUSE FOR ALLOWING MY COMPLACENCY TO CAUSE THIS ERROR AND WILL NOT ALLOW THIS 'GOTCHA' TO 'GET ME' AGAIN. NOT EXCUSES, BUT REQUESTED POSSIBLE FACTORS ARE OFFERED BELOW: DURING MY FIRST 3 RNAV DEPS/ARRS (ON THIS PAIRING), WE WERE VECTORED OFF AND DID NOT FLY RNAV FOR VERY LONG. I MAY HAVE (SUBCONSCIOUSLY) THOUGHT WE'D BE ON A MORE DIRECT CLRNC BY THEN AND NOT BE RNAV-ING. STILL NO EXCUSE THOUGH. THE SPD AND ROUTINE NATURE OF MY ROUTINES CONTRIBUTED TO MY COMPLACENCY. VERY OFTEN WE HEAR 'CLRED AS FILED.' WORKING 11 OUT OF 16 DAYS -- 5 ON, 2 OFF, 5 ON, WITH 1 COMMUTE. RECOMMENDATIONS: FLYING RNAV ARRS/DEPS DECREASES DIALOGUE BTWN PLTS AND CTLRS. DIALOGUE THAT WE ARE USED TO ENABLES MINOR ERRORS OR MISUNDERSTANDING TO BE MORE QUICKLY RESOLVED BEFORE THEY BECOME GROSS ERRORS. THEREFORE HAVE A COMPLETE UNDERSTANDING OF WHERE YOU TOLD THE ACFT TO GO VIA THE DEP/ARR. GO TO A PACE COMMENSURATE WITH CONDITIONS. SPD SHOULD NOT BE FAVORED OVER ACCURACY, ESPECIALLY TOWARDS THE END OF A TRIP. WORK SMARTER, NOT HARDER.
Data retrieved from NASA's ASRS site as of July 2007 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.