 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 captain reported difficulty getting cooperation with ATC concerning which STAR transition to fly.
| Attributes | |
| ACN | 1393844 |
| Time | |
| Date | 201610 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | RSW.Airport |
| State Reference | FL |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | STAR TYNEE1 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 227 Flight Crew Type 20000 |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
On tynee 1 arrival; at initial check-in with approach; reported information XXX. It included that rsw was landing with visual approaches to runway 06. On check-in; approach failed to assign a runway or transition on the STAR. We were only assigned to descend and maintain 6000 ft. Since the RNAV arrival splits in the event of a runway 24 operation; I queried which arrival transition we were to fly; since quick programming would be required if it were to change.the controller replied that she didn't need to assign a runway since I checked in with the ATIS. I then stated that on an RNAV arrival we needed to know the transition. She said she didn't understand what I was asking? In truth; all she needed to do was give me the requested information and provide the service that she is paid to provide. A new controller then took over; gave us a descent; and assigned a heading; now I knew what we needed to do.the first controller was annoyed with my query. Maybe in her mind; it is obvious what is expected in rsw. When it comes to RNAV arrivals; in light of all the complexities involved at numerous airports; I think standardization is extremely important. If they want us to fly a specific transition to a specific runway without conversation then this needs to be spelled out in the ATIS. It was not. Is a change needed to the controller handbook? I do not know.
Original NASA ASRS Text
Title: B737 Captain reported difficulty getting cooperation with ATC concerning which STAR transition to fly.
Narrative: On TYNEE 1 Arrival; at initial check-in with Approach; reported information XXX. It included that RSW was landing with visual approaches to Runway 06. On check-in; Approach failed to assign a runway or transition on the STAR. We were only assigned to descend and maintain 6000 ft. Since the RNAV arrival splits in the event of a Runway 24 operation; I queried which arrival transition we were to fly; since quick programming would be required if it were to change.The Controller replied that she didn't need to assign a runway since I checked in with the ATIS. I then stated that on an RNAV arrival we needed to know the transition. She said she didn't understand what I was asking? In truth; all she needed to do was give me the requested information and provide the service that she is paid to provide. A new Controller then took over; gave us a descent; and assigned a heading; now I knew what we needed to do.The first Controller was annoyed with my query. Maybe in her mind; it is obvious what is expected in RSW. When it comes to RNAV arrivals; in light of all the complexities involved at numerous airports; I think standardization is extremely important. If they want us to fly a specific transition to a specific runway without conversation then this needs to be spelled out in the ATIS. It was not. Is a change needed to the controller handbook? I do not know.
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.