 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ATC and flight crew disagree whether the i-rno localizer or a heading is to be flown departing runway 16R on the rno 4 SID.
| Attributes | |
| ACN | 802647 |
| Time | |
| Date | 200808 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : rno.airport |
| State Reference | NV |
| Altitude | agl single value : 0 msl bound upper : 8000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : rno.tracon |
| Operator | general aviation : personal |
| Make Model Name | P180 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : initial |
| Route In Use | departure : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 125 flight time total : 10200 flight time type : 650 |
| ASRS Report | 802647 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : departure |
| Events | |
| Anomaly | other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued advisory |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance Chart Or Publication |
| Primary Problem | Ambiguous |
| Situations | |
| Chart | airport : rno.airport sid : rno 4 |
Narrative:
Assigned departure procedure was the reno four for our trip to ZZZ. The copilot obtained the ATC clearance and set up the FMS for the flight. During the departure climb; ATC inquired if we were tracking the localizer. I replied we were receiving a navigation flag on 109.9 as that was the first frequency I noticed on the departure chart. The controller's response was that the frequency was 110.9. In either case; this conflicted with the runway 16R departure which calls for an ATC heading to be assigned. No heading was assigned; so we were flying runway heading thinking one would be assigned shortly. We were originally to use runway 16L which does call for tracking i-rno outbound; but our runway was changed to runway 16R when we called for taxi out. I believe this situation arose due to our departure runway change and the departure controller possibly not being informed of this change. As I stated; the runway 16R reno four dp calls for a heading; not localizer tracking like 16L does. Clearance originally gave us runway 16L and I believe that was the origin of the discrepancy of what we were actually doing and what the controller expected. Another note about the departure; both i-rno and i-agy (localizer frequency for runway 16R arrivals) are shown. This is where I picked up the 109.9 frequency during climb which I thought the controller was referring to. However; i-agy is not used for any of the departing runways on that dp per the textual description! In my opinion; it should not even be listed as it has no functional value on this departure. As happened to us; it misled me to select the wrong frequency after the controller queried if we were tracking 'the' localizer for the (controller's perceived?) runway 16L departure (again; runway 16R was our actual departure runway and is a heading departure). I suggest deleting i-agy; 109.9; from the reno four graphic to prevent mistuning navigation equipment.
Original NASA ASRS Text
Title: ATC AND FLT CREW DISAGREE WHETHER THE I-RNO LOC OR A HEADING IS TO BE FLOWN DEPARTING RWY 16R ON THE RNO 4 SID.
Narrative: ASSIGNED DEPARTURE PROCEDURE WAS THE RENO FOUR FOR OUR TRIP TO ZZZ. THE COPILOT OBTAINED THE ATC CLEARANCE AND SET UP THE FMS FOR THE FLIGHT. DURING THE DEPARTURE CLIMB; ATC INQUIRED IF WE WERE TRACKING THE LOCALIZER. I REPLIED WE WERE RECEIVING A NAV FLAG ON 109.9 AS THAT WAS THE FIRST FREQUENCY I NOTICED ON THE DEP CHART. THE CONTROLLER'S RESPONSE WAS THAT THE FREQUENCY WAS 110.9. IN EITHER CASE; THIS CONFLICTED WITH THE RWY 16R DEPARTURE WHICH CALLS FOR AN ATC HEADING TO BE ASSIGNED. NO HEADING WAS ASSIGNED; SO WE WERE FLYING RUNWAY HEADING THINKING ONE WOULD BE ASSIGNED SHORTLY. WE WERE ORIGINALLY TO USE RWY 16L WHICH DOES CALL FOR TRACKING I-RNO OUTBOUND; BUT OUR RUNWAY WAS CHANGED TO RWY 16R WHEN WE CALLED FOR TAXI OUT. I BELIEVE THIS SITUATION AROSE DUE TO OUR DEPARTURE RUNWAY CHANGE AND THE DEPARTURE CONTROLLER POSSIBLY NOT BEING INFORMED OF THIS CHANGE. AS I STATED; THE RWY 16R RENO FOUR DP CALLS FOR A HEADING; NOT LOCALIZER TRACKING LIKE 16L DOES. CLEARANCE ORIGINALLY GAVE US RWY 16L AND I BELIEVE THAT WAS THE ORIGIN OF THE DISCREPANCY OF WHAT WE WERE ACTUALLY DOING AND WHAT THE CONTROLLER EXPECTED. ANOTHER NOTE ABOUT THE DEP; BOTH I-RNO AND I-AGY (LOC FREQ FOR RWY 16R ARRIVALS) ARE SHOWN. THIS IS WHERE I PICKED UP THE 109.9 FREQUENCY DURING CLIMB WHICH I THOUGHT THE CONTROLLER WAS REFERRING TO. HOWEVER; I-AGY IS NOT USED FOR ANY OF THE DEPARTING RUNWAYS ON THAT DP PER THE TEXTUAL DESCRIPTION! IN MY OPINION; IT SHOULD NOT EVEN BE LISTED AS IT HAS NO FUNCTIONAL VALUE ON THIS DEP. AS HAPPENED TO US; IT MISLED ME TO SELECT THE WRONG FREQUENCY AFTER THE CONTROLLER QUERIED IF WE WERE TRACKING 'THE' LOCALIZER FOR THE (CONTROLLER'S PERCEIVED?) RWY 16L DEPARTURE (AGAIN; RWY 16R WAS OUR ACTUAL DEPARTURE RUNWAY AND IS A HEADING DEPARTURE). I SUGGEST DELETING I-AGY; 109.9; FROM THE RENO FOUR GRAPHIC TO PREVENT MISTUNING NAV EQUIPMENT.
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.