37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 602891 |
Time | |
Date | 200312 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : alw.vor |
State Reference | WA |
Altitude | msl bound lower : 14000 msl bound upper : 16000 |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zse.artcc |
Operator | general aviation : personal |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar instruction : trainee other personnel other |
Experience | controller limited radar : 1 controller non radar : 1.5 controller radar : 1 |
ASRS Report | 602891 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar instruction : instructor |
Events | |
Anomaly | other anomaly other |
Independent Detector | atc equipment other atc equipment : radar/mode c other controllera other controllerb other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance none taken : detected after the fact |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
When complete with training/'test flying' an aircraft, B737 requested to be rerouted back to bfi (boeing field) via direct yakima and the chins 5 arrival. I inadvertently amended the route via the correct routing, but to the incorrect airport, sea (seattle-tacoma international). My instructor, the r-side working the sector, and I failed to catch the error before B737 left our airspace. The error was not caught until the aircraft was on final approach into seatac. There was no loss of separation and B737 was rerouted to its correct destination of bfi. What caused the problem was my inexperience. The truth is that I do know better (and do know the difference between the 2 airports), however, there was (evidently) some sort of confusion in the process (or processing) of doing the reroute. One factor that contributed to my 'confusion' is that the 2 airports are about 5 mi apart. The second factor is that I'm only 3 1/2 months 'old' as an ATC specialist. I've caught myself before when doing reroutes, however, the number of errors I made and had to correct had dwindled drastically in the last month to 2 months. With the amount of information and processing that I do daily, it's not surprising that this kind of mistake happened. However, it still is unacceptable that it did. What can be done to prevent this from happening again? Get more experience, be vigilant, don't 'hurry' to do things, double-check my work, and remember that people's lives are counting on the work I do, so I better do it correctly. In thinking and in perspective, remembering that last factor has helped me to focus more and to truly learn from this mistake.
Original NASA ASRS Text
Title: A ZSE RADAR ASSOCIATE TRAINEE INADVERTENTLY REROUTES A B737 TEST FLT TO SEA INSTEAD OF BFI.
Narrative: WHEN COMPLETE WITH TRAINING/'TEST FLYING' AN ACFT, B737 REQUESTED TO BE REROUTED BACK TO BFI (BOEING FIELD) VIA DIRECT YAKIMA AND THE CHINS 5 ARR. I INADVERTENTLY AMENDED THE RTE VIA THE CORRECT ROUTING, BUT TO THE INCORRECT ARPT, SEA (SEATTLE-TACOMA INTL). MY INSTRUCTOR, THE R-SIDE WORKING THE SECTOR, AND I FAILED TO CATCH THE ERROR BEFORE B737 LEFT OUR AIRSPACE. THE ERROR WAS NOT CAUGHT UNTIL THE ACFT WAS ON FINAL APCH INTO SEATAC. THERE WAS NO LOSS OF SEPARATION AND B737 WAS REROUTED TO ITS CORRECT DEST OF BFI. WHAT CAUSED THE PROB WAS MY INEXPERIENCE. THE TRUTH IS THAT I DO KNOW BETTER (AND DO KNOW THE DIFFERENCE BTWN THE 2 ARPTS), HOWEVER, THERE WAS (EVIDENTLY) SOME SORT OF CONFUSION IN THE PROCESS (OR PROCESSING) OF DOING THE REROUTE. ONE FACTOR THAT CONTRIBUTED TO MY 'CONFUSION' IS THAT THE 2 ARPTS ARE ABOUT 5 MI APART. THE SECOND FACTOR IS THAT I'M ONLY 3 1/2 MONTHS 'OLD' AS AN ATC SPECIALIST. I'VE CAUGHT MYSELF BEFORE WHEN DOING REROUTES, HOWEVER, THE NUMBER OF ERRORS I MADE AND HAD TO CORRECT HAD DWINDLED DRASTICALLY IN THE LAST MONTH TO 2 MONTHS. WITH THE AMOUNT OF INFO AND PROCESSING THAT I DO DAILY, IT'S NOT SURPRISING THAT THIS KIND OF MISTAKE HAPPENED. HOWEVER, IT STILL IS UNACCEPTABLE THAT IT DID. WHAT CAN BE DONE TO PREVENT THIS FROM HAPPENING AGAIN? GET MORE EXPERIENCE, BE VIGILANT, DON'T 'HURRY' TO DO THINGS, DOUBLE-CHK MY WORK, AND REMEMBER THAT PEOPLE'S LIVES ARE COUNTING ON THE WORK I DO, SO I BETTER DO IT CORRECTLY. IN THINKING AND IN PERSPECTIVE, REMEMBERING THAT LAST FACTOR HAS HELPED ME TO FOCUS MORE AND TO TRULY LEARN FROM THIS MISTAKE.
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.