 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 flight crew was puzzled when the Q airways on their filed/cleared route were not on their enroute charts.
| Attributes | |
| ACN | 1124460 |
| Time | |
| Date | 201310 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Aero Charts |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
Our pre departure clearance route matched the route uplinked to the FMC; and was verified by both pilots before pushback. Once enroute I took out the hi altitude enroute chart; and was looking over the airways on our flight plan [but] was unable to find some of the airways that we were filed for. After coate intersection we were cleared via Q436 raakk Q438 fnt bae etc. To sfo. The Q airways after coate were unfamiliar to me; so I wanted to look them up on our charts to see the route.we were unable to locate any part of our route after rebbl intersection until fnt (the Q airways) on any hi us or canada charts. We even tried low altitude charts with no luck. Uncomfortable with continuing past rebbl without a published copy of the airways till fnt we asked cle ATC for route confirmation after rebbl. Cle at that point simply cleared us direct oal for the arrival to sfo.problem solved; sort of! To the best of my knowledge the ship set charts were current when we left; but they may not have been; because airways that we were cleared on were nowhere to be found. The charts we were using were revised two months prior to our flight. We were never off course; and no navigation error occurred; yet there was confusion with our charts' accuracy.
Original NASA ASRS Text
Title: A B737 flight crew was puzzled when the Q airways on their filed/cleared route were not on their enroute charts.
Narrative: Our PDC route matched the route uplinked to the FMC; and was verified by both pilots before pushback. Once enroute I took out the HI Altitude enroute chart; and was looking over the airways on our flight plan [but] was unable to find some of the airways that we were filed for. After COATE Intersection we were cleared via Q436 RAAKK Q438 FNT BAE etc. to SFO. The Q airways after COATE were unfamiliar to me; so I wanted to look them up on our charts to see the route.We were unable to locate any part of our route after REBBL Intersection until FNT (the Q airways) on any HI US or Canada charts. We even tried low altitude charts with no luck. Uncomfortable with continuing past REBBL without a published copy of the airways till FNT we asked CLE ATC for route confirmation after REBBL. CLE at that point simply cleared us direct OAL for the arrival to SFO.Problem solved; sort of! To the best of my knowledge the ship set charts were current when we left; but they may not have been; because airways that we were cleared on were nowhere to be found. The charts we were using were revised two months prior to our flight. We were never off course; and no navigation error occurred; yet there was confusion with our charts' accuracy.
Data retrieved from NASA's ASRS site as of July 2013 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.