B747 originally assigned block altitude FL360-FL370 is subsequently assigned FL360; but when xferred to another facility is reported at FL365 by the receiving facility.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	699515
Time
Date	200606
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : zoa.artcc
State Reference	CA
Altitude	msl bound lower : 36000 msl bound upper : 36500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zoa.artcc
Operator	common carrier : air carrier
Make Model Name	B747 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : enroute altitude change
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : non radar
Qualification	controller : radar controller : non radar
Experience	controller non radar : 23 controller radar : 23
ASRS Report	699515
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Supplementary
Problem Areas	Flight Crew Human Performance ATC Facility
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While working position OC3 this morning at ZOA; the following sequence occurred: 1) I climbed air carrier X from FL340 to FL360 to FL370 (block). 2) 13 mins later at XA06; I amended air carrier X altitude; by issuing mops message #26; which was; 'climb to reach FL360 by XB00; report level FL360 for traffic.' 3) after issuing the previous clearance; I expected the data block on air carrier X to read 'climb to FL360.' it did not. It read 'climb FL360-FL370 block altitude.' I perceived this to be a system problem; so I notified the supervisor who is the subject matter expert for the new atop system. After advising the supervisor of what had occurred. 4) he directed me to issue a VHF clearance (does not go to the pilot -- only goes internally through system): 'maintain FL360.' after this; the supervisor directed me to 'demand' an ads report from air carrier X. I did this. 5) subsequently; ZOA received a call from nandi approach control; stating that air carrier X had climbed to FL365 without a clearance. I was advised by management that this was being classified as a pilot deviation.

Original NASA ASRS Text

Title: B747 ORIGINALLY ASSIGNED BLOCK ALT FL360-FL370 IS SUBSEQUENTLY ASSIGNED FL360; BUT WHEN XFERRED TO ANOTHER FACILITY IS RPTED AT FL365 BY THE RECEIVING FACILITY.

Narrative: WHILE WORKING POS OC3 THIS MORNING AT ZOA; THE FOLLOWING SEQUENCE OCCURRED: 1) I CLBED ACR X FROM FL340 TO FL360 TO FL370 (BLOCK). 2) 13 MINS LATER AT XA06; I AMENDED ACR X ALT; BY ISSUING MOPS MESSAGE #26; WHICH WAS; 'CLB TO REACH FL360 BY XB00; RPT LEVEL FL360 FOR TFC.' 3) AFTER ISSUING THE PREVIOUS CLRNC; I EXPECTED THE DATA BLOCK ON ACR X TO READ 'CLB TO FL360.' IT DID NOT. IT READ 'CLB FL360-FL370 BLOCK ALT.' I PERCEIVED THIS TO BE A SYS PROB; SO I NOTIFIED THE SUPVR WHO IS THE SUBJECT MATTER EXPERT FOR THE NEW ATOP SYS. AFTER ADVISING THE SUPVR OF WHAT HAD OCCURRED. 4) HE DIRECTED ME TO ISSUE A VHF CLRNC (DOES NOT GO TO THE PLT -- ONLY GOES INTERNALLY THROUGH SYS): 'MAINTAIN FL360.' AFTER THIS; THE SUPVR DIRECTED ME TO 'DEMAND' AN ADS RPT FROM ACR X. I DID THIS. 5) SUBSEQUENTLY; ZOA RECEIVED A CALL FROM NANDI APCH CTL; STATING THAT ACR X HAD CLBED TO FL365 WITHOUT A CLRNC. I WAS ADVISED BY MGMNT THAT THIS WAS BEING CLASSIFIED AS A PLTDEV.

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.