37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1481366 |
Time | |
Date | 201709 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | RNT.Airport |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
A quick heads-up for renton; wa. If you are a few miles final at renton; runway 34; you are also on or crossing the ILS runway 31L bfi. We were vectored all over the place and then cleared for the visual to 34 rnt from a high right base; maybe 8 miles out. We had rnt clearly in view; the visual loaded and were intercepting final at about the 5 NM point. Rnt tower said we were lined up for the wrong airport and were on final for bfi and to confirm rnt. We were correctly lining up for 34 rnt and never lining up for bfi. We double checked everything and continued for 34. The gotcha and surprise; though it shouldn't have been; is that if we were looking right down the barrel of bfi 31L as we were rolling final runway 34 rnt. As approach cleared us and we swapped over to tower; we were also focusing on the usual myriad of bug smashers. At any rate; there isn't an instrument app to rnt 34; only a visual in the box. The visual has the standard 5 nm final. That pattern should be tighter; though I'm not sure how tight. Crews need to be aware of potential conflict with bfi. Rnt tower said bfi is on the warpath for that conflict. A better vector and setup from approach with a heads-up about what kind of final they needed would have helped. At any rate; no harm. No foul. Approach should have advised us to make the base to final turn at perhaps 3 nm. When checking in with tower they should have advised the same thing. A normal base to final at renton is a conflict with boeing.
Original NASA ASRS Text
Title: Business jet Captain reported that while on a long; high right base to landing at RNT the crew was also lined up during the turn for Runway 31L at BFI.
Narrative: A quick heads-up for Renton; WA. If you are a few miles final at Renton; Runway 34; you are ALSO on or crossing the ILS Runway 31L BFI. We were vectored all over the place and then cleared for the visual to 34 RNT from a HIGH Right Base; maybe 8 miles out. We had RNT clearly in view; the visual loaded and were intercepting final at about the 5 NM point. RNT Tower said we were lined up for the wrong airport and were on final for BFI and to confirm RNT. We were correctly lining up for 34 RNT and NEVER lining up for BFI. We double checked everything and continued for 34. The gotcha and surprise; though it shouldn't have been; is that if we were looking right down the barrel of BFI 31L as we were rolling final RWY 34 RNT. As approach cleared us and we swapped over to tower; we were also focusing on the usual myriad of bug smashers. At any rate; there isn't an instrument app to RNT 34; only a visual in the box. The visual has the standard 5 nm final. That pattern should be tighter; though I'm not sure how tight. Crews need to be aware of potential conflict with BFI. RNT Tower said BFI is on the warpath for that conflict. A better vector and setup from Approach with a heads-up about what kind of final they needed would have helped. At any rate; no harm. No foul. Approach should have advised us to make the base to final turn at perhaps 3 nm. When checking in with tower they should have advised the same thing. A normal base to final at Renton is a CONFLICT with Boeing.
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.