Mco approach controller vectoring an E145 to final, missed a traffic call resulting in a loss of separation with another aircraft on approach to land.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	622440
Time
Date	200406
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mco.airport
State Reference	FL
Altitude	msl single value : 4000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : mco.tracon tower : geg.tower
Operator	common carrier : air carrier
Make Model Name	EMB ERJ 145 ER&LR
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : mco.tracon
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : atp
Experience	flight time last 90 days : 200 flight time total : 4200
ASRS Report	622440
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne critical non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment other atc equipment : radar/mode c aircraft equipment : tcas other flight crewa other flight crewb other other : 3
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 6000 vertical : 200
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

During an approach to mco, we were on a vector with a descent clearance to 3000 ft. Approach control did not notify us of converging traffic. We saw him on TCASII and had a visual of his landing light. We were on a vector heading of 090 degrees. The approach controller sent us through the final approach course, and without notice. We then got a TCASII TA. We started to increase our descent, but because it was head-to-head on conflict, we got an RA to descend. We took action and had about a 3000 FPM descent. We ended up leveling off at clearance altitude, clear of conflict. It wasn't that busy that night, so corrective action of additional controllers wouldn't be the problem. Maybe later at night the controllers should spend less time on the screen. I ended up calling them that night on the ground. The controller was very sorry and said his heart rate was racing. The only contributing factor I see is controller error.

Original NASA ASRS Text

Title: MCO APCH CTLR VECTORING AN E145 TO FINAL, MISSED A TFC CALL RESULTING IN A LOSS OF SEPARATION WITH ANOTHER ACFT ON APCH TO LAND.

Narrative: DURING AN APCH TO MCO, WE WERE ON A VECTOR WITH A DSCNT CLRNC TO 3000 FT. APCH CTL DID NOT NOTIFY US OF CONVERGING TFC. WE SAW HIM ON TCASII AND HAD A VISUAL OF HIS LNDG LIGHT. WE WERE ON A VECTOR HDG OF 090 DEGS. THE APCH CTLR SENT US THROUGH THE FINAL APCH COURSE, AND WITHOUT NOTICE. WE THEN GOT A TCASII TA. WE STARTED TO INCREASE OUR DSCNT, BUT BECAUSE IT WAS HEAD-TO-HEAD ON CONFLICT, WE GOT AN RA TO DSND. WE TOOK ACTION AND HAD ABOUT A 3000 FPM DSCNT. WE ENDED UP LEVELING OFF AT CLRNC ALT, CLR OF CONFLICT. IT WASN'T THAT BUSY THAT NIGHT, SO CORRECTIVE ACTION OF ADDITIONAL CTLRS WOULDN'T BE THE PROB. MAYBE LATER AT NIGHT THE CTLRS SHOULD SPEND LESS TIME ON THE SCREEN. I ENDED UP CALLING THEM THAT NIGHT ON THE GND. THE CTLR WAS VERY SORRY AND SAID HIS HEART RATE WAS RACING. THE ONLY CONTRIBUTING FACTOR I SEE IS CTLR ERROR.

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.