<< >> NASA ASRS Report 772843, February 2008

B737 flight crew reports confusion over altitude restriction at barin on the barin 1 to iad landing runway 19R.

Attributes
ACN	772843
Time
Date	200802
Place
Locale Reference	airport : iad.airport
State Reference	VA
Altitude	msl single value : 6500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pct.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : barin
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 371
ASRS Report	772843
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : published procedure non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued advisory
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

The captain (PF) briefed the barin 1 RNAV arrival into iad in detail and we agreed the following published altitude restr at point barin ('barin at 5000 ft landing runways 1L/right and runway 30; after barin expect radar vectors to final approach course') meant that the 5000 ft altitude restr did not apply because we were told to expect runway 19R. We were subsequently cleared to descend via the barin arrival for runway 19R. Just prior to our arrival at barin; the potomac approach controller questioned us about not making the 5000 ft altitude restr at barin. We were convinced we were right and discussed the wording on the published arrival and pointed out that 'after barin expect...' appeared to be a separate sentence because of the capitalized 'a' beginning 'after.' the controller said it was not a big deal and we politely thanked him for clarifying the instructions. No other aircraft involved and safety was not impacted in any way. I feel this wording is misleading and poorly written. It should be corrected.

Related reports:

• Cl-350 pilot reports confusion regarding the initial climb s...
• An air carrier pilot reported confusion with a crossing rest...
• B737 flight crew reported they failed to make a crossing res...
• Air carrier assigned altitude, then given speed restriction....
• Emb 145 flight crew misses a crossing restriction on arrival...
• Air carrier first officer reports confusion descending into ...

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

Original NASA ASRS Text

Title: B737 FLT CREW REPORTS CONFUSION OVER ALTITUDE RESTRICTION AT BARIN ON THE BARIN 1 TO IAD LANDING RWY 19R.

Narrative: THE CAPT (PF) BRIEFED THE BARIN 1 RNAV ARR INTO IAD IN DETAIL AND WE AGREED THE FOLLOWING PUBLISHED ALT RESTR AT POINT BARIN ('BARIN AT 5000 FT LNDG RWYS 1L/R AND RWY 30; AFTER BARIN EXPECT RADAR VECTORS TO FINAL APCH COURSE') MEANT THAT THE 5000 FT ALT RESTR DID NOT APPLY BECAUSE WE WERE TOLD TO EXPECT RWY 19R. WE WERE SUBSEQUENTLY CLRED TO DSND VIA THE BARIN ARR FOR RWY 19R. JUST PRIOR TO OUR ARR AT BARIN; THE POTOMAC APCH CTLR QUESTIONED US ABOUT NOT MAKING THE 5000 FT ALT RESTR AT BARIN. WE WERE CONVINCED WE WERE RIGHT AND DISCUSSED THE WORDING ON THE PUBLISHED ARR AND POINTED OUT THAT 'AFTER BARIN EXPECT...' APPEARED TO BE A SEPARATE SENTENCE BECAUSE OF THE CAPITALIZED 'A' BEGINNING 'AFTER.' THE CTLR SAID IT WAS NOT A BIG DEAL AND WE POLITELY THANKED HIM FOR CLARIFYING THE INSTRUCTIONS. NO OTHER ACFT INVOLVED AND SAFETY WAS NOT IMPACTED IN ANY WAY. I FEEL THIS WORDING IS MISLEADING AND POORLY WRITTEN. IT SHOULD BE CORRECTED.

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