Flight crew experiences TCASII RA. Controller vectors reporter directly on collision course and says to maintain visual separation and assigned heading.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	322009
Time
Date	199511
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : ptw
State Reference	PA
Altitude	msl bound lower : 13000 msl bound upper : 13400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	other : unknown
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 130 flight time total : 12000 flight time type : 130
ASRS Report	322009
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 210 flight time total : 10000 flight time type : 900
ASRS Report	321938
Events
Anomaly	conflict : nmac non adherence : far
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 400
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

We were tracking ptw 320 degree radial to intercept V64 (psb 113 degree radial) at 13000 ft MSL. Nyc gave us a heading of 315 degrees and pointed out traffic at 2 O'clock at 14000 ft. I acknowledged the traffic was in sight (approximately 7-10 mi). Center then said 'maintain visual climb and maintain 17000 ft MSL' and just prior to this, center told us to intercept V64 on the assigned heading of 315 degrees. We started to climb while setting up the navigation for the capture of J64 assuming our existing heading would clear the traffic at 14000 ft. But the heading was a collision course. We realized this at 13400 ft and descended. My concern is the heading and clearance to climb he gave us was a collision course and then he released us to maintain visual separation. Rather than setting us up on a safe course prior to release and then it being our responsibility if we chose to change course.

Original NASA ASRS Text

Title: FLC EXPERIENCES TCASII RA. CTLR VECTORS RPTR DIRECTLY ON COLLISION COURSE AND SAYS TO MAINTAIN VISUAL SEPARATION AND ASSIGNED HDG.

Narrative: WE WERE TRACKING PTW 320 DEG RADIAL TO INTERCEPT V64 (PSB 113 DEG RADIAL) AT 13000 FT MSL. NYC GAVE US A HDG OF 315 DEGS AND POINTED OUT TFC AT 2 O'CLOCK AT 14000 FT. I ACKNOWLEDGED THE TFC WAS IN SIGHT (APPROX 7-10 MI). CTR THEN SAID 'MAINTAIN VISUAL CLB AND MAINTAIN 17000 FT MSL' AND JUST PRIOR TO THIS, CTR TOLD US TO INTERCEPT V64 ON THE ASSIGNED HDG OF 315 DEGS. WE STARTED TO CLB WHILE SETTING UP THE NAV FOR THE CAPTURE OF J64 ASSUMING OUR EXISTING HDG WOULD CLR THE TFC AT 14000 FT. BUT THE HDG WAS A COLLISION COURSE. WE REALIZED THIS AT 13400 FT AND DSNDED. MY CONCERN IS THE HDG AND CLRNC TO CLB HE GAVE US WAS A COLLISION COURSE AND THEN HE RELEASED US TO MAINTAIN VISUAL SEPARATION. RATHER THAN SETTING US UP ON A SAFE COURSE PRIOR TO RELEASE AND THEN IT BEING OUR RESPONSIBILITY IF WE CHOSE TO CHANGE COURSE.

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.