|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||navaid : ott.vortac|
|Altitude||msl single value : 8500|
|Controlling Facilities||tracon : pct.tracon|
|Operator||common carrier : air carrier|
|Make Model Name||MD-80 Series (DC-9-80) Undifferentiated or Other Model|
|Operating Under FAR Part||Part 121|
|Flight Phase||descent : vacating altitude|
|Route In Use||arrival star : ravnn|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Affiliation||company : air carrier|
|Function||flight crew : first officer|
|Anomaly||altitude deviation : crossing restriction not met|
non adherence : clearance
non adherence : published procedure
|Independent Detector||other controllera|
|Resolutory Action||controller : issued advisory|
none taken : detected after the fact
Flight Crew Human Performance
Chart Or Publication
|Primary Problem||Flight Crew Human Performance|
Our original clearance was OTT6 arrival. ZDC reclred our flight via the ravnn one RNAV arrival. After passing sabbi intersection; potomac approach cleared us to descend via the ravnn one RNAV arrival. The first officer and I looked over the chart several times; and concluded the only remaining crossing restr was at ravnn intersection. After crossing ott; approach informed us that the restr at ott was 9000 ft. Approach stated that there was no traffic conflicts or problems. Flight proceeded to bwi without incident. I encourage commercial chart company to place the altitude under the fix just as all the other fixes are depicted. This is a glaring error on the ravnn arrival that needs to be fixed immediately that will prevent future crews from altdevs. Callback conversation with reporter revealed the following information: when informed that they had missed the crossing restriction at ott the crew was still unable to locate it on the chart. It was not until after parking the aircraft at the gate that the crew was able to locate the restriction on the STAR plate. The reporter states that some aircraft in this air carrier's fleet do not automatically load crossing restrictions when the procedure is selected in the FMC; they must be manually entered. That was the case in this instance.
Original NASA ASRS Text
Title: MD80 CAPTAIN REPORTS MISSING THE CROSSING RESTRICTION AT OTT ON THE RAVNN 1 TO BWI DUE TO PLACEMENT OF RESTRICTION ON COMMERCIAL STAR PLATE.
Narrative: OUR ORIGINAL CLRNC WAS OTT6 ARR. ZDC RECLRED OUR FLT VIA THE RAVNN ONE RNAV ARR. AFTER PASSING SABBI INTXN; POTOMAC APCH CLRED US TO DSND VIA THE RAVNN ONE RNAV ARR. THE FO AND I LOOKED OVER THE CHART SEVERAL TIMES; AND CONCLUDED THE ONLY REMAINING XING RESTR WAS AT RAVNN INTXN. AFTER XING OTT; APCH INFORMED US THAT THE RESTR AT OTT WAS 9000 FT. APCH STATED THAT THERE WAS NO TFC CONFLICTS OR PROBS. FLT PROCEEDED TO BWI WITHOUT INCIDENT. I ENCOURAGE COMMERCIAL CHART COMPANY TO PLACE THE ALT UNDER THE FIX JUST AS ALL THE OTHER FIXES ARE DEPICTED. THIS IS A GLARING ERROR ON THE RAVNN ARR THAT NEEDS TO BE FIXED IMMEDIATELY THAT WILL PREVENT FUTURE CREWS FROM ALTDEVS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: WHEN INFORMED THAT THEY HAD MISSED THE CROSSING RESTRICTION AT OTT THE CREW WAS STILL UNABLE TO LOCATE IT ON THE CHART. IT WAS NOT UNTIL AFTER PARKING THE ACFT AT THE GATE THAT THE CREW WAS ABLE TO LOCATE THE RESTRICTION ON THE STAR PLATE. THE REPORTER STATES THAT SOME ACFT IN THIS ACR'S FLEET DO NOT AUTOMATICALLY LOAD CROSSING RESTRICTIONS WHEN THE PROCEDURE IS SELECTED IN THE FMC; THEY MUST BE MANUALLY ENTERED. THAT WAS THE CASE IN THIS INSTANCE.
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.