 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767 flight crew receives clearance via ESLAR4 departing scel but route manuals and FMC only contain ESLAR3 departure.
| Attributes | |
| ACN | 798163 |
| Time | |
| Date | 200808 |
| Place | |
| Locale Reference | airport : zzz.airport |
| State Reference | US |
| Aircraft 1 | |
| Controlling Facilities | artcc : zzz.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| ASRS Report | 798163 |
| Person 2 | |
| Affiliation | company : air carrier |
| ASRS Report | 798168 |
| Events | |
| Anomaly | non adherence : clearance non adherence : published procedure other spatial deviation |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance |
| Consequence | other |
| Supplementary | |
| Problem Areas | FAA Chart Or Publication Navigational Facility |
| Primary Problem | FAA |
Narrative:
Approximately XA15Z on aug/xa/08 when we copied our ATC clearance the ESLAR4 SID was given. We had the ESLAR3 in our route manual. The aircraft FMC identify page had an active database that also had ESLAR3. Santiago delivery read the ESLAR4. The change is in the wbound leg. ESLAR4 reads inbound to sno NDB on the 076 radial; ESLAR3 reads inbound to sno VOR on the 074 radial. All altitudes and flight distances appear to remain unchanged. We contacted dispatch via satcom. Had ESLAR3 as the current SID. On departure from scel we were assigned FL280. Approximately FL090 while wbound we were attempting to tune sno VOR; but could not get an identify; nor was there a NOTAM that said sno VOR was OTS. Before we could identify the sno NDB identification we were given 'right turn direct sulna' by santiago ATC. No other aircraft on our frequencys; northbound or sbound; had ESLAR4 available.
Original NASA ASRS Text
Title: B767 FLT CREW RECEIVES CLEARANCE VIA ESLAR4 DEPARTING SCEL BUT ROUTE MANUALS AND FMC ONLY CONTAIN ESLAR3 DEPARTURE.
Narrative: APPROX XA15Z ON AUG/XA/08 WHEN WE COPIED OUR ATC CLRNC THE ESLAR4 SID WAS GIVEN. WE HAD THE ESLAR3 IN OUR RTE MANUAL. THE ACFT FMC IDENT PAGE HAD AN ACTIVE DATABASE THAT ALSO HAD ESLAR3. SANTIAGO DELIVERY READ THE ESLAR4. THE CHANGE IS IN THE WBOUND LEG. ESLAR4 READS INBOUND TO SNO NDB ON THE 076 RADIAL; ESLAR3 READS INBOUND TO SNO VOR ON THE 074 RADIAL. ALL ALTS AND FLT DISTANCES APPEAR TO REMAIN UNCHANGED. WE CONTACTED DISPATCH VIA SATCOM. HAD ESLAR3 AS THE CURRENT SID. ON DEP FROM SCEL WE WERE ASSIGNED FL280. APPROX FL090 WHILE WBOUND WE WERE ATTEMPTING TO TUNE SNO VOR; BUT COULD NOT GET AN IDENT; NOR WAS THERE A NOTAM THAT SAID SNO VOR WAS OTS. BEFORE WE COULD IDENT THE SNO NDB ID WE WERE GIVEN 'R TURN DIRECT SULNA' BY SANTIAGO ATC. NO OTHER ACFT ON OUR FREQS; NBOUND OR SBOUND; HAD ESLAR4 AVAILABLE.
Data retrieved from NASA's ASRS site as of May 2009 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.