 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737NG captain reported the fix they were cleared to (daubs) did not appear in either the FMC or their efb.
| Attributes | |
| ACN | 1388802 |
| Time | |
| Date | 201609 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZAB.ARTCC |
| State Reference | NM |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Next Generation Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 144 Flight Crew Type 11000 |
| Events | |
| Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe |
Narrative:
We were cleared direct bna VOR shortly after level off. Upon being handed off to the next sector we were told our route would be modified. Clearance was received to proceed direct to daubs intersection then direct bna fpr. We attempted to type in daubs into the FMC but it did not recognize that as a fix. We reconfirmed the spelling of the point with ZAB ARTCC and attempted to re-input daubs into the FMC but it still would not recognize that point. The pm requested latitude/long and these points were placed in the FMC; executed and LNAV was confirmed. The pm confirmed our bearing to the coordinates given and ZAB ARTCC agreed we were proceeding on the appropriate course. Both pilots inputted daubs into our efb; high and low charts and daubs was not found. Also; looking at the high and low charts on the efb; no points were found in the vicinity of the latitude/longs given. Efb databases were confirmed to be current. Not sure if there was a mistake on our end or our company databases. I would think this not to be an error by ATC.
Original NASA ASRS Text
Title: B737NG Captain reported the fix they were cleared to (DAUBS) did not appear in either the FMC or their EFB.
Narrative: We were cleared direct BNA VOR shortly after level off. Upon being handed off to the next sector we were told our route would be modified. Clearance was received to proceed direct to DAUBS intersection then direct BNA FPR. We attempted to type in DAUBS into the FMC but it did not recognize that as a fix. We reconfirmed the spelling of the point with ZAB ARTCC and attempted to re-input DAUBS into the FMC but it still would not recognize that point. The PM requested LAT/LONG and these points were placed in the FMC; executed and LNAV was confirmed. The PM confirmed our bearing to the coordinates given and ZAB ARTCC agreed we were proceeding on the appropriate course. Both pilots inputted DAUBS into our EFB; High and Low charts and DAUBS was not found. Also; looking at the High and Low charts on the EFB; no points were found in the vicinity of the LAT/LONGs given. EFB databases were confirmed to be current. Not sure if there was a mistake on our end or our Company databases. I would think this not to be an error by ATC.
Data retrieved from NASA's ASRS site 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.