37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1203596 |
Time | |
Date | 201409 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | NCT.TRACON |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Helicopter |
Flight Phase | Cruise |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 14 |
Events | |
Anomaly | Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X called for VFR flight following to sfo from south of mt. Diablo. I issued a code and identified the aircraft. As the aircraft transitioned the oak finals toward the bay; I pointed it out to the woodside sector and initiated a hand off to sfo tower assuming that it would proceed down the bay and direct to sfo. As the aircraft passed the vicinity of sjc and pao; it proceeded on a more southerly course and was leaving my airspace. I inquired if the pilot was still inbound to sfo. At this point oak traffic was building and I determined that the woodside sector could provide better services to the aircraft. I initiated a hand off to woodside; which was accepted and issued the aircraft a frequency change. As the aircraft was proceeding south it flew into the pao tower airspace with no request from the aircraft or coordination by me. Prior to my issuing the frequency change without my noticing; the aircraft proceeded to sfo without further incident.getting the aircraft intended route of flight to sfo would have resolved all problems and allowed for the proper controllers to handle the flight.
Original NASA ASRS Text
Title: NCT Controller reports of an aircraft under flight following and isn't sure of the routing the aircraft is flying. Aircraft enters PAO's Class Delta but isn't pointed out to the Tower.
Narrative: Aircraft X called for VFR flight following to SFO from south of Mt. Diablo. I issued a code and identified the aircraft. As the aircraft transitioned the OAK finals toward the bay; I pointed it out to the Woodside sector and initiated a hand off to SFO tower assuming that it would proceed down the bay and direct to SFO. As the aircraft passed the vicinity of SJC and PAO; it proceeded on a more southerly course and was leaving my airspace. I inquired if the pilot was still inbound to SFO. At this point OAK traffic was building and I determined that the Woodside sector could provide better services to the aircraft. I initiated a hand off to Woodside; which was accepted and issued the aircraft a frequency change. As the aircraft was proceeding south it flew into the PAO tower airspace with no request from the aircraft or coordination by me. Prior to my issuing the frequency change without my noticing; the aircraft proceeded to SFO without further incident.Getting the aircraft intended route of flight to SFO would have resolved all problems and allowed for the proper controllers to handle the flight.
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.