37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1205654 |
Time | |
Date | 201409 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | OAK.Airport |
State Reference | CA |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | Tablet |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
[We had] planned RNAV30 approach into oakland because notams said long term outage of ILS30. Upon reaching norcal approach control; they told us to expect ILS30 which we accepted and began setting up approach in ILS radio head and FMS according to our ipad jepp data. In our printout of fpr and weather/notams was included an ILS30 approach plate dated 26 september. This was not effective for two more days so we both questioned why it was even included in our paper work; and had no indication that it would be a valid approach so we did not reference it. ILS was identified via morse code. Approach controller tried to clear us direct to myfut and intercept the localizer. On our approach plates; this point was not present so we queried approach and he gave us vectors at that time to intercept localizer course. At least two other flights questioned this same clearance from the controller. At this point we were too high to commence the approach so we did a go around to re-enter the pattern. We got vectors to final for ILS30 approach and landed. Because of the confusion of the event; several phone calls transpired between my captain and the duty officer to get a note placed for future crews traveling to oakland so they wouldn't be involved in a similar confusing situation. Multiple airlines are having this issue even as I type this the next day. Apparently; the communication on this approach change has not made it down to the end user.
Original NASA ASRS Text
Title: An A300-600 was cleared for an ILS 30L approach at OAK for which their company provided approach plate was not yet valid and for which their nav data base had no data. Cooperative assistance from ATC ultimately provided the tools to fly the approach.
Narrative: [We had] planned RNAV30 approach into Oakland because notams said long term outage of ILS30. Upon reaching NORCAL approach control; they told us to expect ILS30 which we accepted and began setting up approach in ILS radio head and FMS according to our iPad jepp data. In our printout of FPR and weather/notams was included an ILS30 approach plate dated 26 September. This was not effective for two more days so we both questioned why it was even included in our paper work; and had no indication that it would be a valid approach so we did not reference it. ILS was identified via morse code. Approach controller tried to clear us direct to MYFUT and intercept the localizer. On our approach plates; this point was not present so we queried approach and he gave us vectors at that time to intercept localizer course. At least two other flights questioned this same clearance from the controller. At this point we were too high to commence the approach so we did a go around to re-enter the pattern. We got vectors to final for ILS30 approach and landed. Because of the confusion of the event; several phone calls transpired between my Captain and the duty officer to get a note placed for future crews traveling to Oakland so they wouldn't be involved in a similar confusing situation. Multiple airlines are having this issue even as I type this the next day. Apparently; the communication on this approach change has not made it down to the end user.
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.