37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1634348 |
Time | |
Date | 201904 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SEA.Airport |
State Reference | WA |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Sea was landing runway 16 and ATIS told us to expect an RNAV-Y to runway 16R. Ceilings were approximately 3500' broken. ATC vectored us downwind over puget sound. We were expecting to get clearance to a fix on the RNAV arrival. Instead; the controller cleared us to 'intercept the localizer'. We reminded him that sea was advertising and were expecting the RNAV-Y 16R. He said 'ok; intercept the final approach course.' at this point we were outside of celak. There are three courses on the approach outside of celak. The segment between grify and celak; the segment between paine VOR and agane; and the segment between agane and celak. It wasn't clear which of these segments was intended. My first officer asked me if he wanted me to extend the course from celak but ATC didn't make clear which segment we had been cleared to intercept. All my previous experience with RNAV approaches involve either direct to a fix or intercepting a final approach segment. The vague instructions left us uncertain how to proceed. We decided to see if the autopilot would automatically intercept the 164 course and when it was apparent it didn't; we selected direct celak and the FMA displayed final approach. The ap at that point flew the rest of the approach in accordance with SOP. The selection of direct celak approximated the segment from agane to celak but resulted in a slight overshoot of the extended centerline of the runway. ATC noticed our encroachment onto the final for 16C and advised us to correct back to our final (which had never been specifically assigned). Here was no other traffic inbound at the time the posed any risk of collision. Despite having flown this approach dozens of times in the simulator; I've never gotten a clearance like this. In fact I've never gotten a clearance like that in the real world either. ATC needs to be specific and needs to not assign localizer captures to aircraft who have been told to prepare for an RNAV approach. Furthermore; upon realizing his error; he should have issued more specific instructions rather than just 'intercept the final'. As a flight crew we should have queried ATC and selected direct to celak before an overshoot could occur.
Original NASA ASRS Text
Title: Air carrier Captain reported a track deviation occurred on the arrival into SEA following a confusing clearance from ATC.
Narrative: SEA was landing RWY 16 and ATIS told us to expect an RNAV-Y to RWY 16R. Ceilings were approximately 3500' Broken. ATC vectored us downwind over Puget Sound. We were expecting to get clearance to a fix on the RNAV arrival. Instead; the Controller cleared us to 'intercept the localizer'. We reminded him that SEA was advertising and were expecting the RNAV-Y 16R. He said 'OK; intercept the final approach course.' At this point we were outside of CELAK. There are three courses on the approach outside of CELAK. The segment between GRIFY and CELAK; the segment between Paine VOR and AGANE; and the segment between AGANE and CELAK. It wasn't clear which of these segments was intended. My First Officer asked me if he wanted me to extend the course from CELAK but ATC didn't make clear which segment we had been cleared to intercept. All my previous experience with RNAV approaches involve either direct to a fix or intercepting a final approach segment. The vague instructions left us uncertain how to proceed. We decided to see if the autopilot would automatically intercept the 164 course and when it was apparent it didn't; we selected direct CELAK and the FMA displayed FINAL APPROACH. The AP at that point flew the rest of the approach IAW SOP. The selection of direct CELAK approximated the segment from AGANE to CELAK but resulted in a slight overshoot of the extended centerline of the runway. ATC noticed our encroachment onto the final for 16C and advised us to correct back to our final (which had never been specifically assigned). Here was no other traffic inbound at the time the posed any risk of collision. Despite having flown this approach dozens of times in the simulator; I've never gotten a clearance like this. In fact I've never gotten a clearance like that in the real world either. ATC needs to be specific and needs to not assign localizer captures to aircraft who have been told to prepare for an RNAV approach. Furthermore; upon realizing his error; he should have issued more specific instructions rather than just 'intercept the final'. As a flight crew we should have queried ATC and selected direct to CELAK before an overshoot could occur.
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.