ARTCC radar controller climbed an air carrier CL65 through the altitude of an air carrier B727 in an adjacent sector's airspace after flashing a pointout to that sector, but without getting an approval for the climb. When the conflict alert activated, the reporter shipped the CL65 to the other sector's frequency, but separation was already lost.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	414030
Time
Date	199809
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : bdf
State Reference	IL
Altitude	msl bound lower : 24000 msl bound upper : 24000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau
Operator	common carrier : air carrier
Make Model Name	Challenger CL604
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 6 controller radar : 4
ASRS Report	414030
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment other atc equipment : unspecified other controllera
Resolutory Action	other
Consequence	Other
Miss Distance	horizontal : 20064 vertical : 200
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Air carrier X checked on my frequency climbing to FL230. I climbed the aircraft to FL290 and flashed the data block to the bradford sector. Bradford calls me, pointing the aircraft out to me. I say 'pointout approved' and take the strip down. (Forgetting the aircraft is on my frequency, climbing to FL290 without an approval request.) the aircraft got about 3.8 mi from another air carrier Y at the same altitude in bradford's airspace. Prior to the conflict alert going off, I realized the aircraft was on my frequency and shipped him to bradford. I believed I had taken a pointout and bradford told burlington, the low sector, to climb air carrier X to FL290. I thought burlington must have shipped the aircraft to me by mistake, and immediately put the aircraft on bradford's frequency.

Original NASA ASRS Text

Title: ARTCC RADAR CTLR CLBED AN ACR CL65 THROUGH THE ALT OF AN ACR B727 IN AN ADJACENT SECTOR'S AIRSPACE AFTER FLASHING A POINTOUT TO THAT SECTOR, BUT WITHOUT GETTING AN APPROVAL FOR THE CLB. WHEN THE CONFLICT ALERT ACTIVATED, THE RPTR SHIPPED THE CL65 TO THE OTHER SECTOR'S FREQ, BUT SEPARATION WAS ALREADY LOST.

Narrative: ACR X CHKED ON MY FREQ CLBING TO FL230. I CLBED THE ACFT TO FL290 AND FLASHED THE DATA BLOCK TO THE BRADFORD SECTOR. BRADFORD CALLS ME, POINTING THE ACFT OUT TO ME. I SAY 'POINTOUT APPROVED' AND TAKE THE STRIP DOWN. (FORGETTING THE ACFT IS ON MY FREQ, CLBING TO FL290 WITHOUT AN APPROVAL REQUEST.) THE ACFT GOT ABOUT 3.8 MI FROM ANOTHER ACR Y AT THE SAME ALT IN BRADFORD'S AIRSPACE. PRIOR TO THE CONFLICT ALERT GOING OFF, I REALIZED THE ACFT WAS ON MY FREQ AND SHIPPED HIM TO BRADFORD. I BELIEVED I HAD TAKEN A POINTOUT AND BRADFORD TOLD BURLINGTON, THE LOW SECTOR, TO CLB ACR X TO FL290. I THOUGHT BURLINGTON MUST HAVE SHIPPED THE ACFT TO ME BY MISTAKE, AND IMMEDIATELY PUT THE ACFT ON BRADFORD'S FREQ.

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.