 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Nct controller was questioned regarding an alledged 'wake remant' separation loss; the controller claiming no tools are avaialble to controllers to identify these types of occurrences.
| Attributes | |
| ACN | 1085729 |
| Time | |
| Date | 201304 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | NCT.TRACON |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | A380 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I received notification of an event. When reviewing the playback with management none of us could determine the loss of separation when the event occurred. An A380 departed sfo runway 28 routed to lin VOR. The A380 was initially climbed to 10;000 and vectored northbound offshore in accordance with noise abatement. The A380 was then turned direct lin VOR and climbed to 15;000. The B737-800 departed sfo runway 01 routed over lin; initially climbing to 10;000. The B737-800 was issued another altitude of 8;000. The B737-800 was vectored to a H350 for in trail spacing behind the A380 and climbed to 9;000. When the A380 left 11;000; the B737-800 was climbed to 1;000. The playback reported 4.8 miles and 800 ft 'wake remnants' of the A380 were speculated to be the cause of the separation alert. Controllers have no tools; nor during busy times should be required to know; when and what altitude the aircraft were all along the route. We have no tools that are used to determine any type of wake remnants; nor do we have the ability to remember the altitudes. I challenge any one to work a busy session and remember the altitudes of all aircraft 10 miles prior and all along the route. We work with real time altitudes and real time position of the aircraft.
Original NASA ASRS Text
Title: NCT Controller was questioned regarding an alledged 'wake remant' separation loss; the Controller claiming no tools are avaialble to controllers to identify these types of occurrences.
Narrative: I received notification of an event. When reviewing the playback with management none of us could determine the loss of separation when the event occurred. An A380 departed SFO Runway 28 routed to LIN VOR. The A380 was initially climbed to 10;000 and vectored northbound offshore in accordance with noise abatement. The A380 was then turned direct LIN VOR and climbed to 15;000. The B737-800 departed SFO Runway 01 routed over LIN; initially climbing to 10;000. The B737-800 was issued another altitude of 8;000. The B737-800 was vectored to a H350 for in trail spacing behind the A380 and climbed to 9;000. When the A380 left 11;000; the B737-800 was climbed to 1;000. The playback reported 4.8 miles and 800 FT 'wake remnants' of the A380 were speculated to be the cause of the separation alert. Controllers have no tools; nor during busy times should be required to know; when and what altitude the aircraft were all along the route. We have no tools that are used to determine any type of wake remnants; nor do we have the ability to remember the altitudes. I challenge any one to work a busy session and remember the altitudes of all aircraft 10 miles prior and all along the route. We work with real time altitudes and real time position of the aircraft.
Data retrieved from NASA's ASRS site as of July 2013 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.