37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1263863 |
Time | |
Date | 201505 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | PHL.Airport |
State Reference | PA |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Falcon 2000 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | ILS/VOR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 6000 Flight Crew Type 350 |
Person 2 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer |
Experience | Flight Crew Last 90 Days 95 Flight Crew Total 4300 Flight Crew Type 900 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I was the pilot flying and we were initially expecting the ILS to runway 26 and we had briefed and set up for the ILS 26. After talking with the first approach controller it appeared we were going to be on the ILS 27R. We were given a number of headings and altitude changes while the non flying pilot (nfp) input the ILS 27R into the FMS. On the easy inav the nfp also went to the airport and was trying to select the ILS 27R tail to send the frequency and inbound course to the primary flight display (pfd) and the computer. He inadvertently selected the ILS 27L tail. We were outside of the final approach course on the localizer well before GS intercept when the tower told us to go around because of spacing. We were then vectored around for another approach to ILS 27R again. Since we thought we had the correct frequency and course in the computer I neglected to brief the approach again (which I did not brief the first time for 27R). We then intercepted the localizer for 27L thinking it was 27R and the tower controller told us to make sure we were on the ILS for 27R and told us we were south of course. The needles were right on so we continued. He then asked again to make sure were on the 27R localizer and that's when we double checked the frequency and found it to be for 27L. We promptly switched to 27R and I turned the autopilot off and hand flew the airplane to capture the localizer and GS and hand flew the remaining approach. From the FAF on; the approach was uneventful and we confirmed with tower that he showed us established. This was a very clear reason why every approach should be briefed even when it gets busy or you think you had the correct information in the computer from the first approach after a go around. If I had re-briefed the approach after the switch to 27R we would have noticed that the frequency was wrong even though the FMS was set for 27R. I also had a second chance to brief the approach the second time and still neglected to brief it thinking we had the correct info. This was a simple case of not preparing enough for changes that were made and becoming too comfortable with the computerized system. A briefing should be part of every approach; if multiple are made; and not just the first one.
Original NASA ASRS Text
Title: A DA2000 flight crew reports inadvertently selecting the ILS for Runway 27L when cleared for the ILS 27R. The flight is issued a go-around for spacing issues before the error becomes apparent. On the next approach the error becomes apparent to ATC and the crew eventually corrects the ILS 27R.
Narrative: I was the pilot flying and we were initially expecting the ILS to runway 26 and we had briefed and set up for the ILS 26. After talking with the first approach controller it appeared we were going to be on the ILS 27R. We were given a number of headings and altitude changes while the Non Flying Pilot (NFP) input the ILS 27R into the FMS. On the EASy INAV the NFP also went to the airport and was trying to select the ILS 27R tail to send the frequency and inbound course to the Primary Flight Display (PFD) and the computer. He inadvertently selected the ILS 27L tail. We were outside of the final approach course on the localizer well before GS intercept when the tower told us to go around because of spacing. We were then vectored around for another approach to ILS 27R again. Since we thought we had the correct frequency and course in the computer I neglected to brief the approach again (which I did not brief the first time for 27R). We then intercepted the LOC for 27L thinking it was 27R and the tower controller told us to make sure we were on the ILS for 27R and told us we were south of course. The needles were right on so we continued. He then asked again to make sure were on the 27R LOC and that's when we double checked the frequency and found it to be for 27L. We promptly switched to 27R and I turned the autopilot off and hand flew the airplane to capture the LOC and GS and hand flew the remaining approach. From the FAF on; the approach was uneventful and we confirmed with Tower that he showed us established. This was a very clear reason why every approach should be briefed even when it gets busy or you think you had the correct information in the computer from the first approach after a go around. If I had re-briefed the approach after the switch to 27R we would have noticed that the frequency was wrong even though the FMS was set for 27R. I also had a second chance to brief the approach the second time and still neglected to brief it thinking we had the correct info. This was a simple case of not preparing enough for changes that were made and becoming too comfortable with the computerized system. A briefing should be part of every approach; if multiple are made; and not just the first one.
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.