37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 759566 |
Time | |
Date | 200710 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sps.airport |
State Reference | TX |
Altitude | msl single value : 4500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sps.tracon tower : lax.tower |
Operator | common carrier : air carrier |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern |
Flight Plan | IFR |
Aircraft 2 | |
Operator | other |
Make Model Name | Talon |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 759566 |
Events | |
Anomaly | conflict : nmac |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action |
Miss Distance | vertical : 500 |
Supplementary | |
Problem Areas | Airspace Structure Airport ATC Human Performance Flight Crew Human Performance |
Primary Problem | Airspace Structure |
Situations | |
Airspace Structure | class d : sps.d |
Narrative:
We were approximately 10 mi southwest of the sps VOR at 6000 ft. We were given a clearance to proceed direct to the VOR; cross below 2400 ft and fly the procedure for runway 35. Descending through 4500 ft; the controller came on and said approach clearance was canceled and fly heading 320 degrees. In the background of the transmission was the sound of the radar collision warning. At the same time the TCAS issued a traffic alert depicting an aircraft 400 ft below us and inside the 2.5 mi ring. I immediately stopped the descent and brought the plane back to 4500 ft to try to maintain a 500 ft vertical separation. The first officer said he didn't see the T38 until it passed us. The combination of the TCAS information and the fact the collision warning was going off during the controller's xmissions. The autoplt was immediately disconnected and the aircraft was climbed back to 4500 ft. For some reason even though the TCAS should have issued an RA; it didn't. The controller also said the aircraft came from a 'VFR' pattern at sps which they have no control of; nor do they know if an aircraft is going to be in conflict with arriving passenger aircraft until it's too late. This was the second similar event of that day. Obviously there's something wrong. 1) discontinue military operations during arrival of far part 121 aircraft. 2) proper controller training or accountability of the military to a safety program. I have encountered numerous operrors there I have reported to the commanding officer of the radar installation. Callback conversation with reporter revealed the following information: the reporter stated that he has made numerous flts into sps; also a military training base. When arrivals are landing to the north; T-38's conduct left overhead traffic patterns for runway 33L and T-37's use 33R with right traffic. Commercial carriers are assigned runway 35 and typically arrive from the west over the sps VOR. While descending for an approach; civilian aircraft must descend through the T-38 traffic pattern altitude of 4000 ft. This creates an obvious conflict. The reporter believes that ATC should make an effort to separate traffic when commercial carriers are inbound.
Original NASA ASRS Text
Title: ACR WAS INVOLVED IN NMAC WITH MILITARY ACFT WHILE APPROACHING SPS; A JOINT-USE ARPT.
Narrative: WE WERE APPROX 10 MI SW OF THE SPS VOR AT 6000 FT. WE WERE GIVEN A CLRNC TO PROCEED DIRECT TO THE VOR; CROSS BELOW 2400 FT AND FLY THE PROC FOR RWY 35. DSNDING THROUGH 4500 FT; THE CTLR CAME ON AND SAID APCH CLRNC WAS CANCELED AND FLY HDG 320 DEGS. IN THE BACKGROUND OF THE XMISSION WAS THE SOUND OF THE RADAR COLLISION WARNING. AT THE SAME TIME THE TCAS ISSUED A TFC ALERT DEPICTING AN ACFT 400 FT BELOW US AND INSIDE THE 2.5 MI RING. I IMMEDIATELY STOPPED THE DSCNT AND BROUGHT THE PLANE BACK TO 4500 FT TO TRY TO MAINTAIN A 500 FT VERT SEPARATION. THE FO SAID HE DIDN'T SEE THE T38 UNTIL IT PASSED US. THE COMBINATION OF THE TCAS INFO AND THE FACT THE COLLISION WARNING WAS GOING OFF DURING THE CTLR'S XMISSIONS. THE AUTOPLT WAS IMMEDIATELY DISCONNECTED AND THE ACFT WAS CLBED BACK TO 4500 FT. FOR SOME REASON EVEN THOUGH THE TCAS SHOULD HAVE ISSUED AN RA; IT DIDN'T. THE CTLR ALSO SAID THE ACFT CAME FROM A 'VFR' PATTERN AT SPS WHICH THEY HAVE NO CTL OF; NOR DO THEY KNOW IF AN ACFT IS GOING TO BE IN CONFLICT WITH ARRIVING PAX ACFT UNTIL IT'S TOO LATE. THIS WAS THE SECOND SIMILAR EVENT OF THAT DAY. OBVIOUSLY THERE'S SOMETHING WRONG. 1) DISCONTINUE MIL OPS DURING ARR OF FAR PART 121 ACFT. 2) PROPER CTLR TRAINING OR ACCOUNTABILITY OF THE MIL TO A SAFETY PROGRAM. I HAVE ENCOUNTERED NUMEROUS OPERRORS THERE I HAVE REPORTED TO THE COMMANDING OFFICER OF THE RADAR INSTALLATION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE REPORTER STATED THAT HE HAS MADE NUMEROUS FLTS INTO SPS; ALSO A MIL TRAINING BASE. WHEN ARRIVALS ARE LNDG TO THE NORTH; T-38'S CONDUCT LEFT OVERHEAD TFC PATTERNS FOR RWY 33L AND T-37'S USE 33R WITH RIGHT TFC. COMMERCIAL CARRIERS ARE ASSIGNED RWY 35 AND TYPICALLY ARRIVE FROM THE WEST OVER THE SPS VOR. WHILE DESCENDING FOR AN APCH; CIVILIAN ACFT MUST DESCEND THROUGH THE T-38 TFC PATTERN ALT OF 4000 FT. THIS CREATES AN OBVIOUS CONFLICT. THE REPORTER BELIEVES THAT ATC SHOULD MAKE AN EFFORT TO SEPARATE TFC WHEN COMMERCIAL CARRIERS ARE INBOUND.
Data retrieved from NASA's ASRS site as of January 2009 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.