37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1679515 |
Time | |
Date | 201909 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PAO.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Other VFR Traffic Pattern |
Route In Use | None |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was inbound from the north; north east to land at palo alto. They were a couple miles ahead of aircraft Y who was handed off inbound from the north; who was over taking aircraft X. Due to their relative positions and speed; the most operational advantages and safest route was for aircraft X to enter a right base to runway 31. I used automation to communicate the traffic request to moffett field (nuq 1N). Moffett then called and say unable to aircraft X. This resulted in me trying to communicate a very specific right base entry path for aircraft X that would keep them clear of the nuq delta; which was not successfully done on my part. I had already sequenced aircraft Y to follow aircraft X; who had them in sight and was advised of the overtake. Aircraft X maneuvered towards mid field which resulted in them drifting to extremely close proximity to aircraft Y who was on the mid field side of aircraft X. After aircraft Y reported the aircraft they were following didn't appear to be right base; I gave another instruction for aircraft X to enter right base and then gave alternate following instruction to aircraft Y to follow aircraft X and remain inside the pao delta. I would note that moffett did not appear to have any traffic at all during the time of the event. This type of congestion in the pao airspace is complicated by airspace design where the busier airport (pao) is routinely being denied airspace extensions requests and/ or transitions request skirting the nuq airspace even when it would not affect their operations at all. The current airspace designs are decades old from when nuq was still an active naval airbase and had a very different traffic operations than are routine for current federal air field; which is restricted by the city of sunnyvale in the number of operations it is authorized to have in a year. Palo alto is now a significantly busier airport than moffett and as most aircraft are sequenced into the VFR traffic pattern; routinely needs more airspace that is given by the current airspace design. The pao should be redesigned to allow more room to sequence a VFR traffic pattern to a 3NM final with special consideration given to the northeast quadrant to ensure any expanded airspace doesn't conflict with nuq's departure corridor. I have made this suggestion for airspace redesign more than once. Permission to share a de-identified copy granted.
Original NASA ASRS Text
Title: PAO Tower Controller reported an airspace deviation with an aircraft due to adjacent facility not allowing penetration for sequence.
Narrative: Aircraft X was inbound from the North; North East to land at Palo Alto. They were a couple miles ahead of Aircraft Y who was handed off inbound from the North; who was over taking Aircraft X. Due to their relative positions and speed; the most operational advantages and safest route was for Aircraft X to enter a right base to Runway 31. I used automation to communicate the traffic request to Moffett Field (NUQ 1N). Moffett then called and say unable to Aircraft X. This resulted in me trying to communicate a very specific right base entry path for Aircraft X that would keep them clear of the NUQ Delta; which was not successfully done on my part. I had already sequenced Aircraft Y to follow Aircraft X; who had them in sight and was advised of the overtake. Aircraft X maneuvered towards mid field which resulted in them drifting to extremely close proximity to Aircraft Y who was on the mid field side of Aircraft X. After Aircraft Y reported the aircraft they were following didn't appear to be right base; I gave another instruction for Aircraft X to enter right base and then gave alternate following instruction to Aircraft Y to follow Aircraft X and remain inside the PAO Delta. I would note that Moffett did not appear to have any traffic at all during the time of the event. This type of congestion in the PAO airspace is complicated by airspace design where the busier airport (PAO) is routinely being denied airspace extensions requests and/ or transitions request skirting the NUQ airspace even when it would not affect their operations at all. The current airspace designs are decades old from when NUQ was still an active naval airbase and had a very different traffic operations than are routine for current Federal Air Field; which is restricted by the city of Sunnyvale in the number of operations it is authorized to have in a year. Palo Alto is now a significantly busier airport than Moffett and as most aircraft are sequenced into the VFR traffic pattern; routinely needs more airspace that is given by the current airspace design. The PAO should be redesigned to allow more room to sequence a VFR traffic pattern to a 3NM final with special consideration given to the NE quadrant to ensure any expanded airspace doesn't conflict with NUQ's departure corridor. I have made this suggestion for airspace redesign more than once. Permission to share a de-identified copy granted.
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.