 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier flight crew experiences a track deviation due, in part, to chart issues and short response-time clearance.
| Attributes | |
| ACN | 463850 |
| Time | |
| Date | 200002 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : zny.artcc |
| State Reference | NY |
| Altitude | msl bound lower : 12000 msl bound upper : 24000 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | cruise : enroute altitude change |
| Route In Use | enroute airway : v33.airway |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : multi engine pilot : atp pilot : commercial pilot : instrument |
| Experience | flight time last 90 days : 200 flight time total : 11300 flight time type : 2900 |
| ASRS Report | 463850 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : instrument pilot : commercial pilot : atp |
| Experience | flight time last 90 days : 130 flight time total : 2750 flight time type : 270 |
| ASRS Report | 463346 |
| Events | |
| Anomaly | non adherence : clearance other spatial deviation |
| Independent Detector | other controllera other flight crewa other flight crewb |
| Resolutory Action | controller : issued new clearance |
| Supplementary | |
| Problem Areas | Chart Or Publication Flight Crew Human Performance ATC Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Our flight was cleared from mdt to ord via mdt..har..V33..J64..fwa..OX13 arrival ord. After departing and flying runway heading from runway 31, we received a clearance to 'fly 360 degree heading.' this put us just west of har, the next clearance was to go direct to har and continue via the flight planned route. Since this aircraft is equipped with FMC and was the primary navigation, once we past har going west the FMC dropped har and the subsequent radial (V33) along with the company coordinates (FMC idented HAR13) for the intersection of V33 and J64. I quickly set up my copilot, who was flying, with raw data for har 321 degree radial. While trying to go back and forth with high and low altitude charts to ascertain where J64 intersected V33 and get him set up for the left turn onto J64, we received 3 different altitude changes as well as traffic watch. I requested a direct to ewc but was told 'just stay on your flight planned route.' low altitude charts do not show radials from high altitude charted VOR's. While I was trying to figure all this out, we approached the mid-point on V33, my copilot asked and received NAVAID data for psb to stay on V33. About this time we changed over to another new york ARTCC and asked and got direct ewc. We estimate that we were about 6 mi north of course for J64. We continued to ord, the remainder of the flight was uneventful. Corrective actions/recommendations: in the future I will take more time to preflight the route planning and insert the raw data fixes and radials onto my flight plan where there are V routes and J routes with no intxns. It was impossible to reprogram the FMC with the route because there is no charted intersection of V33 and J64. The only reason it was in the route initially was because it was plotted out by our company dispatchers and coded with the FAA's approval into the FMC. I will also be recommending to the company that we depict these intxns on our flight plan properly in case we are not flying via FMC navigation data.
Original NASA ASRS Text
Title: ACR FLC EXPERIENCES A TRACK DEV DUE, IN PART, TO CHART ISSUES AND SHORT RESPONSE-TIME CLRNC.
Narrative: OUR FLT WAS CLRED FROM MDT TO ORD VIA MDT..HAR..V33..J64..FWA..OX13 ARR ORD. AFTER DEPARTING AND FLYING RWY HEADING FROM RWY 31, WE RECEIVED A CLRNC TO 'FLY 360 DEG HDG.' THIS PUT US JUST W OF HAR, THE NEXT CLRNC WAS TO GO DIRECT TO HAR AND CONTINUE VIA THE FLT PLANNED RTE. SINCE THIS ACFT IS EQUIPPED WITH FMC AND WAS THE PRIMARY NAV, ONCE WE PAST HAR GOING W THE FMC DROPPED HAR AND THE SUBSEQUENT RADIAL (V33) ALONG WITH THE COMPANY COORDINATES (FMC IDENTED HAR13) FOR THE INTXN OF V33 AND J64. I QUICKLY SET UP MY COPLT, WHO WAS FLYING, WITH RAW DATA FOR HAR 321 DEG RADIAL. WHILE TRYING TO GO BACK AND FORTH WITH HIGH AND LOW ALT CHARTS TO ASCERTAIN WHERE J64 INTERSECTED V33 AND GET HIM SET UP FOR THE L TURN ONTO J64, WE RECEIVED 3 DIFFERENT ALT CHANGES AS WELL AS TFC WATCH. I REQUESTED A DIRECT TO EWC BUT WAS TOLD 'JUST STAY ON YOUR FLT PLANNED RTE.' LOW ALT CHARTS DO NOT SHOW RADIALS FROM HIGH ALT CHARTED VOR'S. WHILE I WAS TRYING TO FIGURE ALL THIS OUT, WE APCHED THE MID-POINT ON V33, MY COPLT ASKED AND RECEIVED NAVAID DATA FOR PSB TO STAY ON V33. ABOUT THIS TIME WE CHANGED OVER TO ANOTHER NEW YORK ARTCC AND ASKED AND GOT DIRECT EWC. WE ESTIMATE THAT WE WERE ABOUT 6 MI N OF COURSE FOR J64. WE CONTINUED TO ORD, THE REMAINDER OF THE FLT WAS UNEVENTFUL. CORRECTIVE ACTIONS/RECOMMENDATIONS: IN THE FUTURE I WILL TAKE MORE TIME TO PREFLT THE RTE PLANNING AND INSERT THE RAW DATA FIXES AND RADIALS ONTO MY FLT PLAN WHERE THERE ARE V ROUTES AND J ROUTES WITH NO INTXNS. IT WAS IMPOSSIBLE TO REPROGRAM THE FMC WITH THE RTE BECAUSE THERE IS NO CHARTED INTXN OF V33 AND J64. THE ONLY REASON IT WAS IN THE RTE INITIALLY WAS BECAUSE IT WAS PLOTTED OUT BY OUR COMPANY DISPATCHERS AND CODED WITH THE FAA'S APPROVAL INTO THE FMC. I WILL ALSO BE RECOMMENDING TO THE COMPANY THAT WE DEPICT THESE INTXNS ON OUR FLT PLAN PROPERLY IN CASE WE ARE NOT FLYING VIA FMC NAV DATA.
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.