37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 967586 |
Time | |
Date | 201108 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | BAe 125 Series 800 |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 0 Vertical 300 |
Narrative:
Prior to the FAF while conducting the GPS approach to smo; at the point of getting handed off from socal approach; to contacting the smo tower; we had a TCAS RA event. I do not recall if we got a TA. The traffic was at our 12-1 o'clock at -500 ft. The sic was pilot flying. He disconnected the autopilot and complied with the 'monitor vertical speed' command which called for us to maintain our current altitude. At approximately the FAF; we got the 'clear of conflict'; traffic passed below us at -300 ft. I contacted the tower; informed them of our position; the RA event; and that we had the airport in sight. We were in a position to make a normal approach and landing; so we accepted the new clearance for the visual approach. The approach was stabilized by 1;000 ft AGL; and a normal landing was accomplished. After off-loading the passengers; I debriefed the event with my first officer. We agreed that proper actions were taken; and that neither of us had noticed the traffic prior to the RA. We never saw the aircraft. There was a lot of traffic in the area. I can't believe that this plane had not spoken to any ATC facility who could have warned them of traffic on the approach. I think we could do more training on RA events in congested airspace. At flight safety; it is usually a 'single event' scenario; and is never a surprise.
Original NASA ASRS Text
Title: Hawker 800 Captain experiences a TCAS RA event during GPS approach to SMO near BEVEY. Only leveling off was required to avoid the traffic and the crew continued with a visual approach once clear of conflict was annunciated.
Narrative: Prior to the FAF while conducting the GPS approach to SMO; at the point of getting handed off from SOCAL Approach; to contacting the SMO Tower; we had a TCAS RA event. I do not recall if we got a TA. The traffic was at our 12-1 o'clock at -500 FT. The SIC was pilot flying. He disconnected the autopilot and complied with the 'monitor vertical speed' command which called for us to maintain our current altitude. At approximately the FAF; we got the 'clear of conflict'; traffic passed below us at -300 FT. I contacted the Tower; informed them of our position; the RA event; and that we had the airport in sight. We were in a position to make a normal approach and landing; so we accepted the new clearance for the visual approach. The approach was stabilized by 1;000 FT AGL; and a normal landing was accomplished. After off-loading the passengers; I debriefed the event with my First Officer. We agreed that proper actions were taken; and that neither of us had noticed the traffic prior to the RA. We never saw the aircraft. There was a lot of traffic in the area. I can't believe that this plane had not spoken to any ATC facility who could have warned them of traffic on the approach. I think we could do more training on RA events in congested airspace. At Flight Safety; it is usually a 'single event' scenario; and is never a surprise.
Data retrieved from NASA's ASRS site as of April 2012 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.