37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 538159 |
Time | |
Date | 200202 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bfi.airport |
State Reference | WA |
Altitude | msl single value : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bfi.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 |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | tower : bfi.tower |
Operator | general aviation : personal |
Make Model Name | Cessna Aircraft Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument |
Experience | flight time last 90 days : 10 flight time total : 500 flight time type : 500 |
ASRS Report | 538159 |
Person 2 | |
Affiliation | other |
Function | flight crew : single pilot |
Events | |
Anomaly | non adherence : far non adherence : clearance non adherence : required legal separation other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance controller : separated traffic controller : issued advisory flight crew : executed go around |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Airspace Structure ATC Human Performance Environmental Factor Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I practiced lndgs at bfi. The airport has 2 parallel runways (10001 ft by 200 ft and 3710 ft by 100 ft). Tpa's are 800 ft and 1000 ft respectively. The longer one is controled on 120.6 MHZ and the shorter one on 118.3 MHZ. I was flying the shorter runway 13L/31R pattern with southern flow at the time. I was approaching midfield on the left downwind to runway 13L when the tower advised me to follow cessna on 1 mi final and cleared me for the touch-and-go. I acknowledged. A couple of seconds later, I spotted a cessna on approximately 1 mi final and advised the tower that I had the traffic in sight. I flew an extended downwind leg until this traffic was abeam my left wing and turned base. Only at this moment did it become apparent that the traffic I saw was landing on runway 13R. Not being able to find the traffic I was instructed to follow, I announced myself on left base to runway 13L. The tower advised me to go around because, as the controller put it '...you cut off your traffic.' I acknowledged and followed the instruction never seeing 'my traffic.' it was a bright, clear, sunny day with a little bit of haze. At XA30, the sun was close to being abeam my left wing while on downwind. The traffic I was looking for was very difficult to spot on the city streets backgnd. I was surprised I was able to 'find it.' the runway 13R threshold 'protrudes' 1/4 mi further northwest than runway 13L. Traffic landing on runway 13R looked approximately 1 mi from runway 13L threshold. From the position I was in when first advised to follow another traffic, it was very difficult to judge on which runway the traffic I spotted was landing. I just 'saw/assumed' it was runway 13L. It was a mistake. As for myself, I will never assume anything in a situation like this one. I will fly the extended downwind leg until I actually see the traffic in front of me closing in on the threshold of the runway I intend to land on or will keep asking the tower about its position. The small 'risk' of hearing 'xyz you can start your base now' is much better than what I heard. As for the controllers in an airport with this kind of a layout, with multiple airplanes landing on both runways, with that type of 'lighting' conditions, and radar data available, I think it is desirable to call pilot's base when there is no conflict any longer. So, instead of 'xyz follow abc on 1 mi final clear...' it should be something like 'xyz follow abc on 1 mi final, we will call your base' and give the clearance at that time.
Original NASA ASRS Text
Title: A LOW TIME PVT PLT EXPERIENCES A POTENTIAL CONFLICT WHEN TURNING BASE TOO SOON AFTER SIGHTING THE WRONG TFC ON A POINTOUT FOR RWY 13L AT BFI, WA.
Narrative: I PRACTICED LNDGS AT BFI. THE ARPT HAS 2 PARALLEL RWYS (10001 FT BY 200 FT AND 3710 FT BY 100 FT). TPA'S ARE 800 FT AND 1000 FT RESPECTIVELY. THE LONGER ONE IS CTLED ON 120.6 MHZ AND THE SHORTER ONE ON 118.3 MHZ. I WAS FLYING THE SHORTER RWY 13L/31R PATTERN WITH SOUTHERN FLOW AT THE TIME. I WAS APCHING MIDFIELD ON THE L DOWNWIND TO RWY 13L WHEN THE TWR ADVISED ME TO FOLLOW CESSNA ON 1 MI FINAL AND CLRED ME FOR THE TOUCH-AND-GO. I ACKNOWLEDGED. A COUPLE OF SECONDS LATER, I SPOTTED A CESSNA ON APPROX 1 MI FINAL AND ADVISED THE TWR THAT I HAD THE TFC IN SIGHT. I FLEW AN EXTENDED DOWNWIND LEG UNTIL THIS TFC WAS ABEAM MY L WING AND TURNED BASE. ONLY AT THIS MOMENT DID IT BECOME APPARENT THAT THE TFC I SAW WAS LNDG ON RWY 13R. NOT BEING ABLE TO FIND THE TFC I WAS INSTRUCTED TO FOLLOW, I ANNOUNCED MYSELF ON L BASE TO RWY 13L. THE TWR ADVISED ME TO GO AROUND BECAUSE, AS THE CTLR PUT IT '...YOU CUT OFF YOUR TFC.' I ACKNOWLEDGED AND FOLLOWED THE INSTRUCTION NEVER SEEING 'MY TFC.' IT WAS A BRIGHT, CLR, SUNNY DAY WITH A LITTLE BIT OF HAZE. AT XA30, THE SUN WAS CLOSE TO BEING ABEAM MY L WING WHILE ON DOWNWIND. THE TFC I WAS LOOKING FOR WAS VERY DIFFICULT TO SPOT ON THE CITY STREETS BACKGND. I WAS SURPRISED I WAS ABLE TO 'FIND IT.' THE RWY 13R THRESHOLD 'PROTRUDES' 1/4 MI FURTHER NW THAN RWY 13L. TFC LNDG ON RWY 13R LOOKED APPROX 1 MI FROM RWY 13L THRESHOLD. FROM THE POS I WAS IN WHEN FIRST ADVISED TO FOLLOW ANOTHER TFC, IT WAS VERY DIFFICULT TO JUDGE ON WHICH RWY THE TFC I SPOTTED WAS LNDG. I JUST 'SAW/ASSUMED' IT WAS RWY 13L. IT WAS A MISTAKE. AS FOR MYSELF, I WILL NEVER ASSUME ANYTHING IN A SIT LIKE THIS ONE. I WILL FLY THE EXTENDED DOWNWIND LEG UNTIL I ACTUALLY SEE THE TFC IN FRONT OF ME CLOSING IN ON THE THRESHOLD OF THE RWY I INTEND TO LAND ON OR WILL KEEP ASKING THE TWR ABOUT ITS POS. THE SMALL 'RISK' OF HEARING 'XYZ YOU CAN START YOUR BASE NOW' IS MUCH BETTER THAN WHAT I HEARD. AS FOR THE CTLRS IN AN ARPT WITH THIS KIND OF A LAYOUT, WITH MULTIPLE AIRPLANES LNDG ON BOTH RWYS, WITH THAT TYPE OF 'LIGHTING' CONDITIONS, AND RADAR DATA AVAILABLE, I THINK IT IS DESIRABLE TO CALL PLT'S BASE WHEN THERE IS NO CONFLICT ANY LONGER. SO, INSTEAD OF 'XYZ FOLLOW ABC ON 1 MI FINAL CLR...' IT SHOULD BE SOMETHING LIKE 'XYZ FOLLOW ABC ON 1 MI FINAL, WE WILL CALL YOUR BASE' AND GIVE THE CLRNC AT THAT TIME.
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.