37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 952790 |
Time | |
Date | 201106 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | S56.TRACON |
State Reference | UT |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR SKEES |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 226 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
We were approximately 14 southwest at 9;000 MSL on an assigned southbound heading for a downwind to runway 34R at slc. Flight conditions were day VMC. ATC asked if we had the preceding aircraft in sight. We answered 'yes with airport also in sight'. I incorrectly anticipated the next immediate instruction to be either 'turn left' (for base) or 'cleared visual approach to runway 34R;' and began a very gradual left turn. The 'expected' radio call was not made by ATC; and my early turn resulted in a course deviation before I corrected back to the appropriate heading. I chose to call approach control after arrival at gate and spoke very cordially with the on-duty supervisor. He appreciated the call and explained that the 'later than expected' turn/visual clearance was because of recent trends. He mentioned that the decision had recently been made to delay the issuing of 'visual clearances' because several company aircraft have had to go around due to 'company required' stabilized approach requirements. He stated 'we [local controllers] get gigged' if this happens. There were no conflicts with other aircraft.
Original NASA ASRS Text
Title: After inappropriately beginning a turn to base based on an 'expected' clearance from approach; a B737-300 Captain called the TRACON and learned that controllers had decided to extend downwinds to prevent a growing number of go arounds behind preceding aircraft that were flying company mandated 'stabilized' approaches which caused a loss of separation with the previous 'rules of thumb' used for VMC spacing.
Narrative: We were approximately 14 southwest at 9;000 MSL on an assigned southbound heading for a downwind to Runway 34R at SLC. Flight conditions were day VMC. ATC asked if we had the preceding aircraft in sight. We answered 'yes with airport also in sight'. I incorrectly anticipated the next immediate instruction to be either 'turn left' (for base) or 'cleared visual approach to Runway 34R;' and began a very gradual left turn. The 'expected' radio call was not made by ATC; and my early turn resulted in a course deviation before I corrected back to the appropriate heading. I chose to call Approach Control after arrival at gate and spoke very cordially with the on-duty Supervisor. He appreciated the call and explained that the 'later than expected' turn/visual clearance was because of recent trends. He mentioned that the decision had recently been made to delay the issuing of 'visual clearances' because several Company aircraft have had to go around due to 'Company required' stabilized approach requirements. He stated 'we [Local Controllers] get gigged' if this happens. There were no conflicts with other aircraft.
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.