37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 579224 |
Time | |
Date | 200301 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : pao.airport |
State Reference | CA |
Altitude | msl single value : 600 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : pao.tower |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern arrival : vfr |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | tower : pao.tower |
Make Model Name | PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern arrival : vfr |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 30 flight time total : 240 flight time type : 240 |
ASRS Report | 579224 |
Person 2 | |
Function | flight crew : single pilot |
Events | |
Anomaly | conflict : airborne critical non adherence : required legal separation non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : separated traffic controller : issued alert controller : issued new clearance flight crew : took evasive action flight crew : became reoriented flight crew : executed go around |
Miss Distance | horizontal : 500 vertical : 100 |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
My first approach to landing on runway 31 at pao ended in a go around because I was following the airplane ahead too closely and it had not cleared the runway by the time I was on short final. I made right crosswind and downwind turns, the recommended pattern for runway 31. Abeam the numbers on downwind, I received this clearance: 'cleared to land runway 31, #2 following the cherokee over the amphitheater.' in reality, my plane was #3. There was a low-wing plane on 1/2 to 1 mi final (#1) and the cherokee on about 2 mi final (#2). I assumed that aircraft #1 was the cherokee mentioned in my landing clearance, and I did not know that there was another plane out there (#2, the cherokee). About 20 seconds after getting my landing clearance, I passed abeam aircraft #1. I assumed that it was the cherokee, so I turned right base and was about to turn final when the tower controller barked at me 'aircraft X, you're cutting off your landing traffic, get back to downwind!' the cherokee (#2) was now at my 11 O'clock position, about 100 ft above me, 500 ft away. Had I continued my pattern, we might have collided. I turned left to allow the cherokee to pass, then turned back to final when authority/authorized by tower controller. That authority/authorized actually came too soon, as I was still too close behind the cherokee. Tower authority/authorized a 360 degree, which I executed at final approach speed with full flaps at 600 ft AGL. Then I landed without further excitement. The tower controller committed these errors: 1) clearing me as #2 to land, rather than #3. Other pilots have since told me that the controllers at this airport frequently omit aircraft on short final in counting up the landing aircraft for landing clrncs. I see no reason why they should do this. Tower controllers should count up all aircraft that have not yet landed. 2) use of the 'amphitheater' as a landmark, not shown on the VFR terminal area chart. This airport is not my home base, so when I spotted aircraft #1 on short final, I didn't figure that I needed to ask for a clarification 'unfamiliar amphitheater.' it seemed like a moot point. If I had known that the amphitheater is actually 2 mi out, I would have been more diligent in searching for the cherokee. I had studied the tac prior to this flight (there is very complicated airspace here, with 3 class D's underneath a shelf of class B all within about 8 mi). It does not show the 'amphitheater.' I committed these errors: 1) failure to 'see and avoid' the cherokee until dangerously close, a consequence of failing to visually 'clear' the final approach path while on base. I will be more diligent about this in future. 2) turning base and final too soon after the cherokee had passed. Even though cleared by tower, it is ultimately the pilot's responsibility to decide when adequate separation has been achieved. 3) executing the 360 degrees in slow flight with marginal altitude. Had I made an error, there would have been inadequate altitude to recover from a stall/spin. Recommendations for preventing similar incidents in the future: 1) tower controllers should count all aircraft in the air when issuing #2, #3, etc, landing clrncs. 2) tower controllers should not use the 'amphitheater' as a VFR landmark until it is put on the chart. 3) put the 'amphitheater' on the san francisco VFR terminal area chart. It is an easily-recognized building about 2 mi from the approach end of runway 31 at pao. If the tower is going to use it as a landmark, then let pilots know what it looks like by putting it on the chart. It would fit very nicely on the inset on the back of the tac showing all the other landmarks around pao.
Original NASA ASRS Text
Title: C172 PLT AND A PA28 HAD LESS THAN LEGAL SEPARATION IN PAO CLASS D.
Narrative: MY FIRST APCH TO LNDG ON RWY 31 AT PAO ENDED IN A GAR BECAUSE I WAS FOLLOWING THE AIRPLANE AHEAD TOO CLOSELY AND IT HAD NOT CLRED THE RWY BY THE TIME I WAS ON SHORT FINAL. I MADE R XWIND AND DOWNWIND TURNS, THE RECOMMENDED PATTERN FOR RWY 31. ABEAM THE NUMBERS ON DOWNWIND, I RECEIVED THIS CLRNC: 'CLRED TO LAND RWY 31, #2 FOLLOWING THE CHEROKEE OVER THE AMPHITHEATER.' IN REALITY, MY PLANE WAS #3. THERE WAS A LOW-WING PLANE ON 1/2 TO 1 MI FINAL (#1) AND THE CHEROKEE ON ABOUT 2 MI FINAL (#2). I ASSUMED THAT ACFT #1 WAS THE CHEROKEE MENTIONED IN MY LNDG CLRNC, AND I DID NOT KNOW THAT THERE WAS ANOTHER PLANE OUT THERE (#2, THE CHEROKEE). ABOUT 20 SECONDS AFTER GETTING MY LNDG CLRNC, I PASSED ABEAM ACFT #1. I ASSUMED THAT IT WAS THE CHEROKEE, SO I TURNED R BASE AND WAS ABOUT TO TURN FINAL WHEN THE TWR CTLR BARKED AT ME 'ACFT X, YOU'RE CUTTING OFF YOUR LNDG TFC, GET BACK TO DOWNWIND!' THE CHEROKEE (#2) WAS NOW AT MY 11 O'CLOCK POS, ABOUT 100 FT ABOVE ME, 500 FT AWAY. HAD I CONTINUED MY PATTERN, WE MIGHT HAVE COLLIDED. I TURNED L TO ALLOW THE CHEROKEE TO PASS, THEN TURNED BACK TO FINAL WHEN AUTH BY TWR CTLR. THAT AUTH ACTUALLY CAME TOO SOON, AS I WAS STILL TOO CLOSE BEHIND THE CHEROKEE. TWR AUTH A 360 DEG, WHICH I EXECUTED AT FINAL APCH SPD WITH FULL FLAPS AT 600 FT AGL. THEN I LANDED WITHOUT FURTHER EXCITEMENT. THE TWR CTLR COMMITTED THESE ERRORS: 1) CLRING ME AS #2 TO LAND, RATHER THAN #3. OTHER PLTS HAVE SINCE TOLD ME THAT THE CTLRS AT THIS ARPT FREQUENTLY OMIT ACFT ON SHORT FINAL IN COUNTING UP THE LNDG ACFT FOR LNDG CLRNCS. I SEE NO REASON WHY THEY SHOULD DO THIS. TWR CTLRS SHOULD COUNT UP ALL ACFT THAT HAVE NOT YET LANDED. 2) USE OF THE 'AMPHITHEATER' AS A LANDMARK, NOT SHOWN ON THE VFR TERMINAL AREA CHART. THIS ARPT IS NOT MY HOME BASE, SO WHEN I SPOTTED ACFT #1 ON SHORT FINAL, I DIDN'T FIGURE THAT I NEEDED TO ASK FOR A CLARIFICATION 'UNFAMILIAR AMPHITHEATER.' IT SEEMED LIKE A MOOT POINT. IF I HAD KNOWN THAT THE AMPHITHEATER IS ACTUALLY 2 MI OUT, I WOULD HAVE BEEN MORE DILIGENT IN SEARCHING FOR THE CHEROKEE. I HAD STUDIED THE TAC PRIOR TO THIS FLT (THERE IS VERY COMPLICATED AIRSPACE HERE, WITH 3 CLASS D'S UNDERNEATH A SHELF OF CLASS B ALL WITHIN ABOUT 8 MI). IT DOES NOT SHOW THE 'AMPHITHEATER.' I COMMITTED THESE ERRORS: 1) FAILURE TO 'SEE AND AVOID' THE CHEROKEE UNTIL DANGEROUSLY CLOSE, A CONSEQUENCE OF FAILING TO VISUALLY 'CLR' THE FINAL APCH PATH WHILE ON BASE. I WILL BE MORE DILIGENT ABOUT THIS IN FUTURE. 2) TURNING BASE AND FINAL TOO SOON AFTER THE CHEROKEE HAD PASSED. EVEN THOUGH CLRED BY TWR, IT IS ULTIMATELY THE PLT'S RESPONSIBILITY TO DECIDE WHEN ADEQUATE SEPARATION HAS BEEN ACHIEVED. 3) EXECUTING THE 360 DEGS IN SLOW FLT WITH MARGINAL ALT. HAD I MADE AN ERROR, THERE WOULD HAVE BEEN INADEQUATE ALT TO RECOVER FROM A STALL/SPIN. RECOMMENDATIONS FOR PREVENTING SIMILAR INCIDENTS IN THE FUTURE: 1) TWR CTLRS SHOULD COUNT ALL ACFT IN THE AIR WHEN ISSUING #2, #3, ETC, LNDG CLRNCS. 2) TWR CTLRS SHOULD NOT USE THE 'AMPHITHEATER' AS A VFR LANDMARK UNTIL IT IS PUT ON THE CHART. 3) PUT THE 'AMPHITHEATER' ON THE SAN FRANCISCO VFR TERMINAL AREA CHART. IT IS AN EASILY-RECOGNIZED BUILDING ABOUT 2 MI FROM THE APCH END OF RWY 31 AT PAO. IF THE TWR IS GOING TO USE IT AS A LANDMARK, THEN LET PLTS KNOW WHAT IT LOOKS LIKE BY PUTTING IT ON THE CHART. IT WOULD FIT VERY NICELY ON THE INSET ON THE BACK OF THE TAC SHOWING ALL THE OTHER LANDMARKS AROUND PAO.
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.