 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Controller issued an altitude restriction to a departure air carrier when he observed an unidentified VFR aircraft in close proximity.
| Attributes | |
| ACN | 117247 |
| Time | |
| Date | 198907 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : oak airport : sfo |
| State Reference | CA |
| Altitude | msl bound lower : 9000 msl bound upper : 9500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zoa |
| Operator | common carrier : air carrier |
| Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | departure sid : sid |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 2 |
| ASRS Report | 117247 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | non adherence : far other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | Other |
| Miss Distance | horizontal : 1500 vertical : 300 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
I was working sector 24 r-side at ZOA. This sector works bay area departures from sfo, oak, ngz, sjc to areas northeast. I had 5 or 6 planes climbing out at the time. 2 were being ladder up 1000' apart from each other. Bay approach was shipping aircraft to center out of 4000' climbing to FL230 all day. Bay approach owns 13,000' and below. They gave me air carrier X out of 4000-5000' climbing to FL230. I climbed him and gave him normal speed. I had a conflict alert going off at the time on 2 other aircraft. When I was suppressing the conflict my d-side said look at that limited data block in front of air carrier X. It was only a mile in front of air carrier X. I told air carrier X to maintain present altitude and he leveled off at 9000'. Controllers are supposed to resolve all conflicts before shipping aircraft to another controller's frequency unless otherwise coordinated. I think bay approach has a bad habit of shipping aircraft too low in their airspace to get rid of them.
Original NASA ASRS Text
Title: CTLR ISSUED AN ALT RESTRICTION TO A DEP ACR WHEN HE OBSERVED AN UNIDENTIFIED VFR ACFT IN CLOSE PROX.
Narrative: I WAS WORKING SECTOR 24 R-SIDE AT ZOA. THIS SECTOR WORKS BAY AREA DEPS FROM SFO, OAK, NGZ, SJC TO AREAS NE. I HAD 5 OR 6 PLANES CLIMBING OUT AT THE TIME. 2 WERE BEING LADDER UP 1000' APART FROM EACH OTHER. BAY APCH WAS SHIPPING ACFT TO CENTER OUT OF 4000' CLIMBING TO FL230 ALL DAY. BAY APCH OWNS 13,000' AND BELOW. THEY GAVE ME ACR X OUT OF 4000-5000' CLIMBING TO FL230. I CLIMBED HIM AND GAVE HIM NORMAL SPEED. I HAD A CONFLICT ALERT GOING OFF AT THE TIME ON 2 OTHER ACFT. WHEN I WAS SUPPRESSING THE CONFLICT MY D-SIDE SAID LOOK AT THAT LIMITED DATA BLOCK IN FRONT OF ACR X. IT WAS ONLY A MILE IN FRONT OF ACR X. I TOLD ACR X TO MAINTAIN PRESENT ALT AND HE LEVELED OFF AT 9000'. CTLRS ARE SUPPOSED TO RESOLVE ALL CONFLICTS BEFORE SHIPPING ACFT TO ANOTHER CTLR'S FREQ UNLESS OTHERWISE COORDINATED. I THINK BAY APCH HAS A BAD HABIT OF SHIPPING ACFT TOO LOW IN THEIR AIRSPACE TO GET RID OF THEM.
Data retrieved from NASA's ASRS site as of August 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.