37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 344341 |
Time | |
Date | 199608 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : ngp |
State Reference | TX |
Altitude | msl bound lower : 1400 msl bound upper : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : crp |
Operator | other |
Make Model Name | Mentor (T-34) |
Operating Under FAR Part | other : other |
Flight Phase | cruise other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | other |
Make Model Name | Mentor (T-34) |
Operating Under FAR Part | other : other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
ASRS Report | 344341 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | conflict : airborne less severe non adherence : required legal separation |
Independent Detector | atc equipment other atc equipment : unspecified other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Miss Distance | horizontal : 7500 vertical : 100 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
MTR X was being vectored for a PAR runway 13R approach when MTR Y was executing his assigned climb out of runway heading until 2.5 DME then turn left to 40 degrees to maintain 1500 ft. The controller was busy and apparently forgot about the MTR Y coming off and turning right in his flight path of MTR X. A supervisor was standing right there and witnessed the entire event and did not do anything other than relieve the controller eventually. The conflict alert went off 3 different times and I later verified this by looking at the ARTS-ii printout which indicated as follows: 1) 1.73 mi, 2) 1.14 mi, and 3) 1.17 mi all within 100-200 ft vertical separation. I witnessed the entire event from the sector immediately next to the involved sector and was within 1 ft (seating side by side) of the controller listening to all that was going on. By the time visual separation was applied it was clearly too late!!!
Original NASA ASRS Text
Title: CTLR SITTING NEXT TO NGP APCH CTLR SAW LTSS OCCUR BTWN 2 T34 ACFT, ONE ON A VECTOR FOR A PAR APCH TO NGP AND THE OTHER ON A DEP PROC WHICH TURNED THE ACFT INTO THE 534 ON THE VECTOR. CONFLICT ALERT ACTIVATED AND SUPVR WAS WATCHING INCIDENT.
Narrative: MTR X WAS BEING VECTORED FOR A PAR RWY 13R APCH WHEN MTR Y WAS EXECUTING HIS ASSIGNED CLB OUT OF RWY HDG UNTIL 2.5 DME THEN TURN L TO 40 DEGS TO MAINTAIN 1500 FT. THE CTLR WAS BUSY AND APPARENTLY FORGOT ABOUT THE MTR Y COMING OFF AND TURNING R IN HIS FLT PATH OF MTR X. A SUPVR WAS STANDING RIGHT THERE AND WITNESSED THE ENTIRE EVENT AND DID NOT DO ANYTHING OTHER THAN RELIEVE THE CTLR EVENTUALLY. THE CONFLICT ALERT WENT OFF 3 DIFFERENT TIMES AND I LATER VERIFIED THIS BY LOOKING AT THE ARTS-II PRINTOUT WHICH INDICATED AS FOLLOWS: 1) 1.73 MI, 2) 1.14 MI, AND 3) 1.17 MI ALL WITHIN 100-200 FT VERT SEPARATION. I WITNESSED THE ENTIRE EVENT FROM THE SECTOR IMMEDIATELY NEXT TO THE INVOLVED SECTOR AND WAS WITHIN 1 FT (SEATING SIDE BY SIDE) OF THE CTLR LISTENING TO ALL THAT WAS GOING ON. BY THE TIME VISUAL SEPARATION WAS APPLIED IT WAS CLRLY TOO LATE!!!
Data retrieved from NASA's ASRS site as of July 2007 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.