37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1203142 |
Time | |
Date | 201409 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Person 1 | |
Function | Pilot Not Flying Captain |
Experience | Flight Crew Last 90 Days 130 Flight Crew Total 11100 Flight Crew Type 1750 |
Person 2 | |
Function | First Officer Pilot Flying |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Overshoot Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy |
Narrative:
While on approach; we were cleared down to 2000 feet; direct an intersection to join the localizer; cleared the visual approach; and maintain 210 knots until the initial approach fix (IAF). We were on the localizer; after IAF and prior to interception of the glideslope level at 2000 feet. We were in the process of slowing and configuring the aircraft for glideslope intercept. My first officer was the pilot flying. Just prior to interception of the glideslope; the approach controller told us we had traffic at our 11 o'clock; 1.5 miles; which was a FAA flight check aircraft who had us in sight and was maintaining visual separation. At first; being night I could not visually see the traffic. I saw on TCAS that the traffic was only a mile away; 300 feet below us and heading right toward us. I then got a visual on the landing light of this traffic and it was indeed heading toward us at nearly our assigned altitude. We then received a resolution advisory (RA); the first officer did a great job of turning off the autopilot and hand flying the RA to keep us away from this traffic that appeared to be on a collision course with us as well as climbing toward us. We were on the localizer as instructed flying our visual approach when to our surprise; this FAA flight check aircraft was cutting across the localizer in a perpendicular fashion heading toward us. We climbed and missed the flight check aircraft by about 300 feet vertically. Thank god for TCAS! I informed ATC that we were responding to an RA. When the conflict was over; we had more that enough distance from the airport to reestablish a stabilized approach and landing and we landing without further incident. After landing I asked the tower to give me the phone number to the TRACON. I spoke with the approach control supervisor who said it was indeed unusual and he would have their quality control people look into it.
Original NASA ASRS Text
Title: A B737 at 2;000 FT on an ILS approach took evasive action after a TCAS RA from a FAA Flight Check aircraft while both were under ATC control. The other aircraft reported the B737 insight but took no evasive action.
Narrative: While on approach; we were cleared down to 2000 Feet; direct an intersection to join the localizer; cleared the visual approach; and maintain 210 knots until the initial approach fix (IAF). We were on the localizer; after IAF and prior to interception of the Glideslope level at 2000 feet. We were in the process of slowing and configuring the aircraft for Glideslope Intercept. My First Officer was the pilot flying. Just prior to interception of the Glideslope; the approach controller told us we had traffic at our 11 o'clock; 1.5 miles; which was a FAA flight Check aircraft who had us in sight and was maintaining visual separation. At first; being night I could not visually see the traffic. I saw on TCAS that the traffic was only a mile away; 300 feet below us and heading right toward us. I then got a visual on the landing light of this traffic and it was indeed heading toward us at nearly our assigned altitude. We then received a resolution advisory (RA); the First Officer did a great job of turning off the autopilot and hand flying the RA to keep us away from this traffic that appeared to be on a collision course with us as well as climbing toward us. We were on the localizer as instructed flying our visual approach when to our surprise; this FAA Flight Check Aircraft was cutting across the localizer in a perpendicular fashion heading toward us. We climbed and missed the Flight Check aircraft by about 300 feet vertically. Thank God for TCAS! I informed ATC that we were responding to an RA. When the conflict was over; we had more that enough distance from the airport to reestablish a stabilized approach and landing and we landing without further incident. After landing I asked the Tower to give me the phone number to the TRACON. I spoke with the Approach Control Supervisor who said it was indeed unusual and he would have their quality control people look into it.
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.