EMS-helicopter experiences airborne conflict with air carrier-medium large transport while transiting arsa and in contact with and control of approach controller.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	136308
Time
Date	199002
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : zzz
State Reference	US
Altitude	msl bound lower : 2000 msl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : zzz
Operator	common carrier : air taxi
Make Model Name	Helicopter
Flight Phase	cruise other
Flight Plan	None
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : initial climbout : takeoff climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	other other : other pilot : commercial pilot : instrument
Experience	flight time last 90 days : 30 flight time total : 3050 flight time type : 150
ASRS Report	136308
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne less severe non adherence other
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 600 vertical : 500
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation Inter Facility Coordination Failure

Narrative:

Departed YYY on EMS mission to XXX. Contacted ZZZ approach 2-3 mi west of YYY for traffic advisories through arsa. At 4-5 mi northeast of abc airport, I questioned approach control as to whether he wanted me to contact tower or stay with him. He responded 'stay with me,' with no traffic advisories, vectors, etc. I then presumed all was quiet at ZZZ and proceeded direct, which took me toward the departure end of 01L at ZZZ. At about 1/2-1 mi northeast of 01L, I noticed an air carrier medium large transport Y climbing out from 01L, and due to projected flight paths and proximity, made a right turn to avoid the aircraft and his wake. Contributing factors include a lack of potential traffic conflict information from approach controller, not transferred to tower while operating in tower area, little or no traffic on approach frequency, and mission related traffic on company frequencys. The purpose of an arsa is to provide IFR/VFR traffic advisories and conflict resolution (aim). I think approach control should have informed me about the departing traffic or transferred me to tower.

Original NASA ASRS Text

Title: EMS-HELICOPTER EXPERIENCES AIRBORNE CONFLICT WITH ACR-MLG WHILE TRANSITING ARSA AND IN CONTACT WITH AND CTL OF APCH CTLR.

Narrative: DEPARTED YYY ON EMS MISSION TO XXX. CONTACTED ZZZ APCH 2-3 MI W OF YYY FOR TFC ADVISORIES THROUGH ARSA. AT 4-5 MI NE OF ABC ARPT, I QUESTIONED APCH CTL AS TO WHETHER HE WANTED ME TO CONTACT TWR OR STAY WITH HIM. HE RESPONDED 'STAY WITH ME,' WITH NO TFC ADVISORIES, VECTORS, ETC. I THEN PRESUMED ALL WAS QUIET AT ZZZ AND PROCEEDED DIRECT, WHICH TOOK ME TOWARD THE DEP END OF 01L AT ZZZ. AT ABOUT 1/2-1 MI NE OF 01L, I NOTICED AN ACR MLG Y CLBING OUT FROM 01L, AND DUE TO PROJECTED FLT PATHS AND PROX, MADE A RIGHT TURN TO AVOID THE ACFT AND HIS WAKE. CONTRIBUTING FACTORS INCLUDE A LACK OF POTENTIAL TFC CONFLICT INFO FROM APCH CTLR, NOT TRANSFERRED TO TWR WHILE OPERATING IN TWR AREA, LITTLE OR NO TFC ON APCH FREQ, AND MISSION RELATED TFC ON COMPANY FREQS. THE PURPOSE OF AN ARSA IS TO PROVIDE IFR/VFR TFC ADVISORIES AND CONFLICT RESOLUTION (AIM). I THINK APCH CTL SHOULD HAVE INFORMED ME ABOUT THE DEPARTING TFC OR TRANSFERRED ME TO TWR.

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.