ZAU controller described possible operational deviation as adjacent controller started to descend aircraft early without proper coordination; no operational deviation or operational error recorded.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	701505
Time
Date	200606
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : fwa.airport
State Reference	IN
Altitude	msl single value : 23000
Environment
Flight Conditions	IMC
Weather Elements	Thunderstorm
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau.artcc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zau.artcc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 4 controller time certified in position2 : 5
ASRS Report	701505
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	airspace violation : entry conflict : airborne less severe non adherence : required legal separation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued alert controller : issued new clearance
Consequence	faa : investigated
Miss Distance	horizontal : 30000
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

Aircraft #1 was deviating south of course for WX at FL230; with the gsh sector and through bearz airspace. After the aircraft informed that they were going direct fwa the aircraft was xferred to the olk sector. A couple of mins later the conflict alert went off with aircraft #2 as they were passing. Aircraft #2 came from the fwa hi sector at FL240 assigned 270 degree heading. After crossing the gsh/olk lateral boundary the aircraft was given a descent to 170 and a clearance to cgt. The airspace deviation is from this initial descent; the aircraft was less than 2.5 mi (about 2.4 or 2.3 mi) from the boundary when they started their descent. As the aircraft was descending the conflict alert went off with aircraft #1 as they were passing. Then a pointout was given to the olk sector to protect another boundary.

Original NASA ASRS Text

Title: ZAU CTLR DESCRIBED POSSIBLE OPDEV AS ADJACENT CTLR STARTED TO DSND ACFT EARLY WITHOUT PROPER COORD; NO OPDEV OR OPERROR RECORDED.

Narrative: ACFT #1 WAS DEVIATING S OF COURSE FOR WX AT FL230; WITH THE GSH SECTOR AND THROUGH BEARZ AIRSPACE. AFTER THE ACFT INFORMED THAT THEY WERE GOING DIRECT FWA THE ACFT WAS XFERRED TO THE OLK SECTOR. A COUPLE OF MINS LATER THE CONFLICT ALERT WENT OFF WITH ACFT #2 AS THEY WERE PASSING. ACFT #2 CAME FROM THE FWA HI SECTOR AT FL240 ASSIGNED 270 DEG HDG. AFTER XING THE GSH/OLK LATERAL BOUNDARY THE ACFT WAS GIVEN A DSCNT TO 170 AND A CLRNC TO CGT. THE AIRSPACE DEV IS FROM THIS INITIAL DSCNT; THE ACFT WAS LESS THAN 2.5 MI (ABOUT 2.4 OR 2.3 MI) FROM THE BOUNDARY WHEN THEY STARTED THEIR DSCNT. AS THE ACFT WAS DSNDING THE CONFLICT ALERT WENT OFF WITH ACFT #1 AS THEY WERE PASSING. THEN A POINTOUT WAS GIVEN TO THE OLK SECTOR TO PROTECT ANOTHER BOUNDARY.

Data retrieved from NASA's ASRS site as of January 2009 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.