37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 882368 |
Time | |
Date | 201004 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | SMF.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR FLUNK |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | Conflict Airborne Conflict |
Narrative:
Air carrier X was inbound to smf on the flunk arrival. I had an un-targeted VFR at 7;400 ft that was potential traffic for the aircraft. I instructed air carrier X to increase rate of descent through 7;000 and called the traffic. Shortly afterward air carrier X called smf in sight. I replied that he needed to continue his rate of descent through 7;000 and leaving 7;000 they were cleared for a visual approach to runway 16L. About thirty seconds to a minute later; air carrier X advised me that they were going to level off at their current altitude. I observed that they were approximately 2 miles southeast of the VFR target about one hundred feet above. I told air carrier X negative; continue through 7;000 for the traffic; traffic indicates 7;400. Air carrier X then reported that they were receiving an RA and climbing back up to 8;000. I replied with a roger and called traffic again; passing 2 miles north. Air carrier X reported traffic in sight. I cleared air carrier X for a visual approach. Recommendation: no recommendation; however; the actions of the pilot; even though it was an RA; actually made the situation worse instead of better. If they had continued on the descent; they would have been below the traffic with plenty of room. Leveling off at the altitude of the traffic called doesn't seem like the best of ideas. I did not use any further methods of separation; i.e. Vectors; because I observed lateral separation was going to work as well.
Original NASA ASRS Text
Title: NCT Controller described TCAS RA event when air carrier inbound to SMF was issued traffic; instructed to continue descent to clear traffic but responded to a TCAS climb; reporter suggesting TCAS response made potential conflict more critical.
Narrative: Air Carrier X was inbound to SMF on the FLUNK arrival. I had an un-targeted VFR at 7;400 ft that was potential traffic for the aircraft. I instructed Air Carrier X to increase rate of descent through 7;000 and called the traffic. Shortly afterward Air Carrier X called SMF in sight. I replied that he needed to continue his rate of descent through 7;000 and leaving 7;000 they were cleared for a visual approach to Runway 16L. About thirty seconds to a minute later; Air Carrier X advised me that they were going to level off at their current altitude. I observed that they were approximately 2 miles southeast of the VFR target about one hundred feet above. I told Air Carrier X negative; continue through 7;000 for the traffic; traffic indicates 7;400. Air Carrier X then reported that they were receiving an RA and climbing back up to 8;000. I replied with a Roger and called traffic again; passing 2 miles north. Air Carrier X reported traffic in sight. I cleared Air Carrier X for a visual approach. Recommendation: No recommendation; however; the actions of the Pilot; even though it was an RA; actually made the situation worse instead of better. If they had continued on the descent; they would have been below the traffic with plenty of room. Leveling off at the altitude of the traffic called doesn't seem like the best of ideas. I did not use any further methods of separation; i.e. vectors; because I observed lateral separation was going to work as well.
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.