ATC cleared aircraft X to an altitude that was not coordinated with the adjacent sector, and in the climb would be in conflict with aircraft Y. The receiving controller was alert enough to catch the miscue, but too late to avoid the operational error.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	423302
Time
Date	199812
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : aco
State Reference	OH
Altitude	msl bound lower : 33000 msl bound upper : 33000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Fokker 100
Operating Under FAR Part	Part 121
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 180 flight time total : 10000 flight time type : 600
ASRS Report	423302
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 210 flight time total : 8000 flight time type : 1000
ASRS Report	423433
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	faa : investigated
Miss Distance	horizontal : 25800 vertical : 1700
Supplementary
Air Traffic Incident	Operational Error

Narrative:

We were level at FL290. ATC then cleared us to FL370 and told us to contact ZOB. When we checked in on the other ZOB frequency, we stated we were passing FL330 climbing to FL370. ATC asked us to confirm our cleared altitude. When we repeated FL370 he asked us to immediately maintain FL330. I disconnected the autoplt and descended about 200 ft back to FL330. A few mins later, the controller advised us that we were suspected of deviating an ATC clearance and told us to contact them via phone when we landed at phl. When we landed at phl and phoned ZOB, the supervisor informed us that he had pulled the recording of our conversation with the previous controller and found that the controller had indeed given us clearance to FL370. He further stated that the controller would be 'written up' for his error and that no enforcement action would be taken against us.

Original NASA ASRS Text

Title: ATC CLRED ACFT X TO AN ALT THAT WAS NOT COORDINATED WITH THE ADJACENT SECTOR, AND IN THE CLB WOULD BE IN CONFLICT WITH ACFT Y. THE RECEIVING CTLR WAS ALERT ENOUGH TO CATCH THE MISCUE, BUT TOO LATE TO AVOID THE OPERROR.

Narrative: WE WERE LEVEL AT FL290. ATC THEN CLRED US TO FL370 AND TOLD US TO CONTACT ZOB. WHEN WE CHKED IN ON THE OTHER ZOB FREQ, WE STATED WE WERE PASSING FL330 CLBING TO FL370. ATC ASKED US TO CONFIRM OUR CLRED ALT. WHEN WE REPEATED FL370 HE ASKED US TO IMMEDIATELY MAINTAIN FL330. I DISCONNECTED THE AUTOPLT AND DSNDED ABOUT 200 FT BACK TO FL330. A FEW MINS LATER, THE CTLR ADVISED US THAT WE WERE SUSPECTED OF DEVIATING AN ATC CLRNC AND TOLD US TO CONTACT THEM VIA PHONE WHEN WE LANDED AT PHL. WHEN WE LANDED AT PHL AND PHONED ZOB, THE SUPVR INFORMED US THAT HE HAD PULLED THE RECORDING OF OUR CONVERSATION WITH THE PREVIOUS CTLR AND FOUND THAT THE CTLR HAD INDEED GIVEN US CLRNC TO FL370. HE FURTHER STATED THAT THE CTLR WOULD BE 'WRITTEN UP' FOR HIS ERROR AND THAT NO ENFORCEMENT ACTION WOULD BE TAKEN AGAINST US.

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.