 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B757 captain expressed frustration regarding ATC services provided by S46 TRACON and sea tower regarding runway and speed assignments and overall ATC techniques.
| Attributes | |
| ACN | 630658 |
| Time | |
| Date | 200408 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : sea.airport |
| State Reference | WA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : s46.tracon tower : sea.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer & glide slope : 16r |
| Flight Phase | descent : approach |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| ASRS Report | 630658 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Situations | |
| ATC Facility | procedure or policy : s46.tracon procedure or policy : sea.tower |
Narrative:
Was told to expect the ILS runway 16R at seattle by seattle approach control. At the last possible moment, they cleared us for a visual approach to runway 16L and told us to contact seattle tower. Seattle tower wanted us to maintain 220 KTS to boeing field (3.9 NM from the runway 16L touchdown zone) due to 'a heavy' behind us that was landing on runway 16R. On short final we got a TCASII RA and never was able to identify where it came from. After flying into the seattle airport during the month of aug/xa/04, in my opinion, this kind of sloppy operation seems to be the rule rather than the exception. Very late runway changes are commonplace. Requests for high speeds to 'make it fit' are not uncommon. In the above example,it would have been impossible to comply with seattle tower's request and execute a stable approach from 1000 ft AGL.
Original NASA ASRS Text
Title: B757 CAPT EXPRESSED FRUSTRATION REGARDING ATC SVCS PROVIDED BY S46 TRACON AND SEA TWR REGARDING RWY AND SPD ASSIGNMENTS AND OVERALL ATC TECHNIQUES.
Narrative: WAS TOLD TO EXPECT THE ILS RWY 16R AT SEATTLE BY SEATTLE APCH CTL. AT THE LAST POSSIBLE MOMENT, THEY CLRED US FOR A VISUAL APCH TO RWY 16L AND TOLD US TO CONTACT SEATTLE TWR. SEATTLE TWR WANTED US TO MAINTAIN 220 KTS TO BOEING FIELD (3.9 NM FROM THE RWY 16L TOUCHDOWN ZONE) DUE TO 'A HVY' BEHIND US THAT WAS LNDG ON RWY 16R. ON SHORT FINAL WE GOT A TCASII RA AND NEVER WAS ABLE TO IDENT WHERE IT CAME FROM. AFTER FLYING INTO THE SEATTLE ARPT DURING THE MONTH OF AUG/XA/04, IN MY OPINION, THIS KIND OF SLOPPY OP SEEMS TO BE THE RULE RATHER THAN THE EXCEPTION. VERY LATE RWY CHANGES ARE COMMONPLACE. REQUESTS FOR HIGH SPDS TO 'MAKE IT FIT' ARE NOT UNCOMMON. IN THE ABOVE EXAMPLE,IT WOULD HAVE BEEN IMPOSSIBLE TO COMPLY WITH SEATTLE TWR'S REQUEST AND EXECUTE A STABLE APCH FROM 1000 FT AGL.
Data retrieved from NASA's ASRS site as of July 2007 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.