<< >> NASA ASRS Report 373529, July 1997

Pilot deviation when flight crew misread the STAR and started a descent for an expected altitude crossing.

Attributes
ACN	373529
Time
Date	199707
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : ogd
State Reference	UT
Altitude	msl bound lower : 26200 msl bound upper : 27000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zlc
Operator	common carrier : air carrier
Make Model Name	B737-200
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	cruise other descent other
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar pilot : private
Experience	controller non radar : 9 controller radar : 7 flight time total : 60
ASRS Report	373529
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 8000 flight time type : 4000
ASRS Report	373944
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Publication	Unspecified

Narrative:

Aircraft #1 was descending to FL270 and cleared via the BEARR2 arrival. Mode C indicated that the aircraft was descending lower than FL270 so I asked the aircraft what their altitude was. The response was 'leaving FL262 for 15000 ft, we were cleared on the BEARR2 arrival.' I then advised the aircraft that the assigned altitude was FL270. He stated that he was only complying with what was published. (Only altitudes that are on the charts are expect altitudes.) this seems to be a reoccurring problem, especially on this arrival. It is only a matter of time before an aircraft will descend at the wrong time and cause a loss of separation. Supplemental information from acn 373944: 'cleared BEARR2 arrival landing south' the STAR reads expect 15000 ft at bearr. I put 15000 ft in the MCP and figured my descent point and left FL270 for 15000 ft. The cause of the problem was I didn't read the STAR correctly. The box at bearr is an expect altitude not a hard altitude.

Related reports:

• Heading track deviation during a STAR arrival. ATC expected ...
• Heading track deviation occurs as medium large transport fli...
• A B737-200 flight crew flies an expected route in deviation ...
• An alleged, insinuated heading track deviation by departure ...
• Pilot's perception of what was expected from ATC's possibly ...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: PLTDEV WHEN FLC MISREAD THE STAR AND STARTED A DSCNT FOR AN EXPECTED ALT XING.

Narrative: ACFT #1 WAS DSNDING TO FL270 AND CLRED VIA THE BEARR2 ARR. MODE C INDICATED THAT THE ACFT WAS DSNDING LOWER THAN FL270 SO I ASKED THE ACFT WHAT THEIR ALT WAS. THE RESPONSE WAS 'LEAVING FL262 FOR 15000 FT, WE WERE CLRED ON THE BEARR2 ARR.' I THEN ADVISED THE ACFT THAT THE ASSIGNED ALT WAS FL270. HE STATED THAT HE WAS ONLY COMPLYING WITH WHAT WAS PUBLISHED. (ONLY ALTS THAT ARE ON THE CHARTS ARE EXPECT ALTS.) THIS SEEMS TO BE A REOCCURRING PROB, ESPECIALLY ON THIS ARR. IT IS ONLY A MATTER OF TIME BEFORE AN ACFT WILL DSND AT THE WRONG TIME AND CAUSE A LOSS OF SEPARATION. SUPPLEMENTAL INFO FROM ACN 373944: 'CLRED BEARR2 ARR LNDG S' THE STAR READS EXPECT 15000 FT AT BEARR. I PUT 15000 FT IN THE MCP AND FIGURED MY DSCNT POINT AND LEFT FL270 FOR 15000 FT. THE CAUSE OF THE PROB WAS I DIDN'T READ THE STAR CORRECTLY. THE BOX AT BEARR IS AN EXPECT ALT NOT A HARD ALT.

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.