 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A track deviation occurred as a result of an air carrier flight crew's failure to xchk the clearance route with the FMS programmed route.
| Attributes | |
| ACN | 302380 |
| Time | |
| Date | 199504 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : atl |
| State Reference | GA |
| Altitude | msl bound lower : 18000 msl bound upper : 23000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | artcc : ztl |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 120 flight time total : 6000 flight time type : 1500 |
| ASRS Report | 302380 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | non adherence : clearance non adherence other other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Flight was filed for route between atl and srq as katl, direct atl VOR, direct taylor and then the rest of the route. Typical departure out of atl with radar vectors. Climbing through about 18000 ft MSL, center cleared flight to 'turn left intercept J89.' just prior to intercept of course from atl to tay, ATC asked if we intended to intercept J89. It was assumed that J89 was course inbound to taylor as this was what was on our clearance. Captain and I relied on magenta line and did not xchk with en route charts. A vague clearance and complacency on our part resulted in ATC thinking we were doing something that we weren't - ie, intercepting the airway. Solution: if a clearance isn't specific as to route and fix, query the controller and xchk that what you are cleared correspond to how you are filed and what is loaded in the FMS computer.
Original NASA ASRS Text
Title: A TRACK DEV OCCURRED AS A RESULT OF AN ACR FLC'S FAILURE TO XCHK THE CLRNC RTE WITH THE FMS PROGRAMMED RTE.
Narrative: FLT WAS FILED FOR RTE BTWN ATL AND SRQ AS KATL, DIRECT ATL VOR, DIRECT TAYLOR AND THEN THE REST OF THE RTE. TYPICAL DEP OUT OF ATL WITH RADAR VECTORS. CLBING THROUGH ABOUT 18000 FT MSL, CTR CLRED FLT TO 'TURN L INTERCEPT J89.' JUST PRIOR TO INTERCEPT OF COURSE FROM ATL TO TAY, ATC ASKED IF WE INTENDED TO INTERCEPT J89. IT WAS ASSUMED THAT J89 WAS COURSE INBOUND TO TAYLOR AS THIS WAS WHAT WAS ON OUR CLRNC. CAPT AND I RELIED ON MAGENTA LINE AND DID NOT XCHK WITH ENRTE CHARTS. A VAGUE CLRNC AND COMPLACENCY ON OUR PART RESULTED IN ATC THINKING WE WERE DOING SOMETHING THAT WE WEREN'T - IE, INTERCEPTING THE AIRWAY. SOLUTION: IF A CLRNC ISN'T SPECIFIC AS TO RTE AND FIX, QUERY THE CTLR AND XCHK THAT WHAT YOU ARE CLRED CORRESPOND TO HOW YOU ARE FILED AND WHAT IS LOADED IN THE FMS COMPUTER.
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.