 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767-300 flight crew reported confusion on a missed approach at bfi when ATC expected them to descend rather than climb.
| Attributes | |
| ACN | 1309054 |
| Time | |
| Date | 201511 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | BFI.Airport |
| State Reference | WA |
| Environment | |
| Flight Conditions | IMC |
| Light | Dawn |
| Aircraft 1 | |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 27 Flight Crew Total 10000 Flight Crew Type 7500 |
| Person 2 | |
| Function | Pilot Not Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 80 Flight Crew Total 16000 Flight Crew Type 5000 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
On ILS 13R at bfi (11-1 page) G/south and localizer captured (in IMC). At approximately 1900 ft; inside isoge we get a line through GS; automatic pilot light. Aircraft loses the GS and basically waffles in air. No chance of reintercepting GS. We decide to go-around; execute our procedures and inform ATC. ATC tells us to descend to 1500 ft and track localizer. We elect to level off. In GA mode and a heavy 767 didn't think it prudent to enter a descent to 1500. ATC gives climb and vectors. Points out traffic which we acknowledge. Second approach was uneventful. During second approach; we asked ATC map instructions in case it happened again and they told us to descend to 1500 and track localizer. After landing told to call sea TRACON. TRACON got our story. Also told us we're expected to descend on the GA to 1500 ft due to traffic going into seatac. TRACON described it as a 'very unusual procedure'. He also told us there was conflict with another aircraft. The causal factor in this incident is the missed approach procedure for 13R. Nowhere in the procedure does it tell you to descend to 1500 ft especially 7 miles from the airport. I have never heard of a map procedure that requires you to descend on a go-around. So even if the descent was published; not sure that is the safest way to do a map. TRACON described it as a 'very unusual procedure' but nowhere is there any info highlighting or describing the procedure and the reason for it. In addition; we were also in the 13th hour of duty. We diverted earlier because of weather.
Original NASA ASRS Text
Title: B767-300 flight crew reported confusion on a missed approach at BFI when ATC expected them to descend rather than climb.
Narrative: On ILS 13R at BFI (11-1 page) G/S and LOC captured (in IMC). At approximately 1900 ft; inside ISOGE we get a line through GS; AUTO PILOT light. Aircraft loses the GS and basically waffles in air. No chance of reintercepting GS. We decide to go-around; execute our procedures and inform ATC. ATC tells us to descend to 1500 ft and track LOC. We elect to level off. In GA mode and a heavy 767 didn't think it prudent to enter a descent to 1500. ATC gives climb and vectors. Points out traffic which we acknowledge. Second approach was uneventful. During second approach; we asked ATC MAP instructions in case it happened again and they told us to descend to 1500 and track LOC. After landing told to call SEA TRACON. TRACON got our story. Also told us we're expected to descend on the GA to 1500 ft due to traffic going into SeaTac. TRACON described it as a 'very unusual procedure'. He also told us there was conflict with another aircraft. The causal factor in this incident is the Missed Approach Procedure for 13R. Nowhere in the procedure does it tell you to descend to 1500 ft especially 7 miles from the airport. I have never heard of a MAP procedure that requires you to descend on a go-around. So even if the descent was published; not sure that is the safest way to do a MAP. TRACON described it as a 'very unusual procedure' but nowhere is there any info highlighting or describing the procedure and the reason for it. In addition; we were also in the 13th hour of duty. We diverted earlier because of weather.
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.