 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
While conducting an approach the flight crew encountered unknown VFR traffic in close proximity which was not displaying on TCAS; possibly due to no or inoperative transponder. ATC was queried and requested help in identifying the aircraft type. No RA was generated by this event.
| Attributes | |
| ACN | 1270639 |
| Time | |
| Date | 201506 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Flight Plan | None |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Conflict NMAC |
Narrative:
On approach to runway 11 in stl; at approximately 2;500 feet crossing just inside hixob; we encountered a single engine aircraft that crossed our flight path estimated at 300-500 feet above our altitude. The aircraft was not displaying on our TCAS as it appears he did not have a transponder on. We reported the traffic to ATC on stl tower 118.5 and inquired about the traffic. The controller stated he had just started intermittently picking up a primary target. Another controller came on and inquired if we knew what type of aircraft it was. Pilot monitoring (pm) stated it appeared to be a [small aircraft]. No TCAS RA was encountered due to the traffic not being displayed. It appears that the aircraft was near the boarder of; or possibly within the class B airspace; however; ATC was not aware of the aircraft in time to notify us of the potential conflict. The flight continued with no further incident.the VFR aircraft was not displaying a transponder or in communication with ATC.
Original NASA ASRS Text
Title: While conducting an approach the flight crew encountered unknown VFR traffic in close proximity which was not displaying on TCAS; possibly due to no or inoperative transponder. ATC was queried and requested help in identifying the aircraft type. No RA was generated by this event.
Narrative: On approach to Runway 11 in STL; at approximately 2;500 feet crossing just inside HIXOB; we encountered a single engine aircraft that crossed our flight path estimated at 300-500 feet above our altitude. The aircraft was not displaying on our TCAS as it appears he did not have a transponder on. We reported the traffic to ATC on STL Tower 118.5 and inquired about the traffic. The controller stated he had just started intermittently picking up a primary target. Another controller came on and inquired if we knew what type of aircraft it was. Pilot Monitoring (PM) stated it appeared to be a [small aircraft]. No TCAS RA was encountered due to the traffic not being displayed. It appears that the aircraft was near the boarder of; or possibly within the class B airspace; however; ATC was not aware of the aircraft in time to notify us of the potential conflict. The flight continued with no further incident.The VFR aircraft was not displaying a transponder or in communication with ATC.
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.