Flight crew on DC9 inbound to atl on rome 2 arrival missed the erlin crossing because the first officer misread the chart. 18 DME from the rmg VOR was set instead of 7 DME.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	415586
Time
Date	199810
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : atl
State Reference	GA
Altitude	msl bound lower : 13000 msl bound upper : 13800
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : atl
Operator	common carrier : air carrier
Make Model Name	DC-9 10
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	arrival other arrival star : star
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : instrument pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 17000 flight time type : 8000
ASRS Report	415586
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : flight engineer pilot : commercial
Experience	flight time last 90 days : 150 flight time total : 7400 flight time type : 3100
ASRS Report	415587
Events
Anomaly	altitude deviation : crossing restriction not met altitude deviation : undershoot non adherence : clearance
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Given erlin crossing at 13000 ft and 250 KTS per STAR rome 2 arrival. First officer misread erlin at 18 DME due to the way it is shown on the STAR rome 2 arrival. If you look at the STAR, the (D18) arrow could be easily confused or misread, as we did. The actual crossing of erlin at 13800 ft and 280 KTS. This happened on a VFR day we could see no conflict of other aircraft. I told the controller we would make a turn, he said that it would not be necessary. Callback conversation with reporter revealed the following information: reporter said he should have caught the error but assumed the first officer had correctly set the distance for the crossing restr. He said in a discussion with the first officer after landing, they both felt the double arrow was confusing. He was scheduled for a 6 month pilot check and planned to ask the instructor about the 2 arrows.

Original NASA ASRS Text

Title: FLC ON DC9 INBOUND TO ATL ON ROME 2 ARR MISSED THE ERLIN XING BECAUSE THE FO MISREAD THE CHART. 18 DME FROM THE RMG VOR WAS SET INSTEAD OF 7 DME.

Narrative: GIVEN ERLIN XING AT 13000 FT AND 250 KTS PER STAR ROME 2 ARR. FO MISREAD ERLIN AT 18 DME DUE TO THE WAY IT IS SHOWN ON THE STAR ROME 2 ARR. IF YOU LOOK AT THE STAR, THE (D18) ARROW COULD BE EASILY CONFUSED OR MISREAD, AS WE DID. THE ACTUAL XING OF ERLIN AT 13800 FT AND 280 KTS. THIS HAPPENED ON A VFR DAY WE COULD SEE NO CONFLICT OF OTHER ACFT. I TOLD THE CTLR WE WOULD MAKE A TURN, HE SAID THAT IT WOULD NOT BE NECESSARY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR SAID HE SHOULD HAVE CAUGHT THE ERROR BUT ASSUMED THE FO HAD CORRECTLY SET THE DISTANCE FOR THE XING RESTR. HE SAID IN A DISCUSSION WITH THE FO AFTER LNDG, THEY BOTH FELT THE DOUBLE ARROW WAS CONFUSING. HE WAS SCHEDULED FOR A 6 MONTH PLT CHK AND PLANNED TO ASK THE INSTRUCTOR ABOUT THE 2 ARROWS.

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.