 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier attempted to secure expected routing information from ATC but the communication was confused.
| Attributes | |
| ACN | 928353 |
| Time | |
| Date | 201101 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZSE.ARTCC |
| State Reference | WA |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | MD-83 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 270 Flight Crew Total 5000 Flight Crew Type 2000 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
We had just leveled off at FL330 and were in contact with a center controller working the lower altitude enroute area around sea. For traffic and our routing the controller gave us a heading. We responded; 'can we expect rufus intersection?' in an attempt to prompt an expect______ clearance should we go NORDO. The controller stated 'the next controller will have on-course for you'. We asked what we could expect should we lose radio contact. The response was 'we haven't had any radio outages in this area'. We of course considered that this particular aircraft might have the radio go out regardless of how well center was doing. The controller didn't appear to understand the necessity for an expected fix when giving a blind vector and then handing off an aircraft to another frequency. This report is submitted to prompt instruction at this facility or for this controller so this doesn't become habit.
Original NASA ASRS Text
Title: Air Carrier attempted to secure expected routing information from ATC but the communication was confused.
Narrative: We had just leveled off at FL330 and were in contact with a Center Controller working the lower altitude enroute area around SEA. For traffic and our routing the Controller gave us a heading. We responded; 'Can we expect RUFUS Intersection?' in an attempt to prompt an Expect______ clearance should we go NORDO. The Controller stated 'The next Controller will have on-course for you'. We asked what we could expect should we lose radio contact. The response was 'We haven't had any radio outages in this area'. We of course considered that this particular aircraft might have the radio go out regardless of how well Center was doing. The Controller didn't appear to understand the necessity for an expected fix when giving a blind vector and then handing off an aircraft to another frequency. This report is submitted to prompt instruction at this facility or for this Controller so this doesn't become habit.
Data retrieved from NASA's ASRS site as of April 2012 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.