37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 701540 |
Time | |
Date | 200606 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : atl.airport |
State Reference | GA |
Altitude | msl bound lower : 2500 msl bound upper : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : a80.tracon |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 170/175 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : initial |
Route In Use | departure sid : atl 5 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 3000 flight time type : 450 |
ASRS Report | 701540 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | controller : provided flight assist controller : issued advisory |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Chart Or Publication |
Primary Problem | Chart Or Publication |
Situations | |
Chart | sid : atl5. atl |
Narrative:
Upon climb out of atl; tower handed us off to departure. (We had departed runway 9L.) the controller had simply said 'contact departure.' we switched over to frequency 125.00 per the atl 5 departure (ATL5.atl) commercial chart 10-3 mar/11/05. We could hear people talking but the controller never responded until about 3 mins later when he stated that 125.00 was a tower frequency and to contact 135.7. When we contacted that controller; he seemed irritated and began vectoring us around traffic. When we inquired about the frequency off of the chart; he stated that it was incorrect and that our charts were wrong. Clearance had never given us a departure frequency; more than likely due to the fact that it was supposed to be on the chart. Upon inquiring with dispatch; we verified that our charts were indeed current. We never received a TCAS alert and the controller did not say anymore about the situation. I believe the sole cause was the incorrect frequency on the chart; but I believe it would be beneficial to have clearance delivery make it a standard practice to give pilots the departure frequency.
Original NASA ASRS Text
Title: AN ERJ170 PLT RPTS THE ATL5.ATL CHART IN USE THE DAY OF HIS FLT LISTED THE INCORRECT DEP CTL FREQ CAUSING A NORDO EVENT FOR APPROX 3 MINS.
Narrative: UPON CLBOUT OF ATL; TWR HANDED US OFF TO DEP. (WE HAD DEPARTED RWY 9L.) THE CTLR HAD SIMPLY SAID 'CONTACT DEP.' WE SWITCHED OVER TO FREQ 125.00 PER THE ATL 5 DEP (ATL5.ATL) COMMERCIAL CHART 10-3 MAR/11/05. WE COULD HEAR PEOPLE TALKING BUT THE CTLR NEVER RESPONDED UNTIL ABOUT 3 MINS LATER WHEN HE STATED THAT 125.00 WAS A TWR FREQ AND TO CONTACT 135.7. WHEN WE CONTACTED THAT CTLR; HE SEEMED IRRITATED AND BEGAN VECTORING US AROUND TFC. WHEN WE INQUIRED ABOUT THE FREQ OFF OF THE CHART; HE STATED THAT IT WAS INCORRECT AND THAT OUR CHARTS WERE WRONG. CLRNC HAD NEVER GIVEN US A DEP FREQ; MORE THAN LIKELY DUE TO THE FACT THAT IT WAS SUPPOSED TO BE ON THE CHART. UPON INQUIRING WITH DISPATCH; WE VERIFIED THAT OUR CHARTS WERE INDEED CURRENT. WE NEVER RECEIVED A TCAS ALERT AND THE CTLR DID NOT SAY ANYMORE ABOUT THE SITUATION. I BELIEVE THE SOLE CAUSE WAS THE INCORRECT FREQ ON THE CHART; BUT I BELIEVE IT WOULD BE BENEFICIAL TO HAVE CLRNC DELIVERY MAKE IT A STANDARD PRACTICE TO GIVE PLTS THE DEP FREQ.
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.