37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1029554 |
Time | |
Date | 201208 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Airbus 318/319/320/321 Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Beechcraft Twin Turboprop or Jet Undifferentiated or Other Model |
Flight Phase | Climb |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Narrative:
An airbus on vectors to the ILS runway 30 approach lgb heading north bound 030. A king air departed sna opposite direction on a local VFR code with sba in his scratch pad. Initial call I ask if he wants flight following to sba? [It] seemed weird to me that he would come off on a local code to sba which is out of sct airspace. He then advised he wanted to pick up his IFR flight plan to sba. I looked over at the departure controller and asked if he would get me his IFR strip to sba. Since there was no prior coordination; as there usually is when they depart IFR; I had no idea what he wanted. I then realized the airbus was approaching the final approach course and turned and descended/cleared him for the ILS approach. The king air was then level at 2;400 ft 2 miles north of the final; I then climbed the king air and told him to expedite his climb for airbus traffic 11 o'clock and 3 miles. While I was instructing the king air to climb; unannounced to me the airbus started a climb in response to a TCAS RA from the king air. The king air; while reading back his climb instructions; advised me that the he had the airbus in sight and that the airbus appeared to be climbing. The airbus then advised that he was responding to a TCAS RA and was climbing. The king air advised that he was turning right in response to the climbing airbus. While this was happening; the towers were opening; the line was ringing from ful and toa tower was calling over the shout line. A heads up would have been nice. It would have saved me coordinating with the king air.
Original NASA ASRS Text
Title: SCT Controller described a conflict event between a LGB Air Carrier arrival and a VFR King Air departing SNA seeking an IFR clearance; the reporter indicting a heads-up from SNA Tower would have eased the situation.
Narrative: An Airbus on vectors to the ILS Runway 30 Approach LGB heading north bound 030. A King Air departed SNA opposite direction on a local VFR code with SBA in his scratch pad. Initial call I ask if he wants flight following to SBA? [It] seemed weird to me that he would come off on a local code to SBA which is out of SCT airspace. He then advised he wanted to pick up his IFR flight plan to SBA. I looked over at the Departure Controller and asked if he would get me his IFR strip to SBA. Since there was no prior coordination; as there usually is when they depart IFR; I had no idea what he wanted. I then realized the Airbus was approaching the final approach course and turned and descended/cleared him for the ILS approach. The King Air was then level at 2;400 FT 2 miles north of the final; I then climbed the King Air and told him to expedite his climb for Airbus traffic 11 o'clock and 3 miles. While I was instructing the King Air to climb; unannounced to me the Airbus started a climb in response to a TCAS RA from the King Air. The King Air; while reading back his climb instructions; advised me that the he had the Airbus in sight and that the Airbus appeared to be climbing. The Airbus then advised that he was responding to a TCAS RA and was climbing. The King Air advised that he was turning right in response to the climbing Airbus. While this was happening; the Towers were opening; the line was ringing from FUL and TOA Tower was calling over the shout line. A heads up would have been nice. It would have saved me coordinating with the King Air.
Data retrieved from NASA's ASRS site as of July 2013 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.