Narrative:

We were cleared for the MAREO2 departure and assigned runway 23L for departure. The ILS 23L DME was notamed out of service (ifvj). For departure off 23L the MAREO2 departure reads; 'climb on heading 227 to ifvj 2.3 DME then on assigned heading 210; 227; or 242.' without an operable ifvj DME you can not comply with the departure. The reason that I point this out is that the DME for 23L and other ind runways is periodically notamed out of service. Whenever this happens ind clearance still issues clearances that are predicated on these items being operable. In these cases I will notify either ground control or clearance delivery that we are unable the departure. From those interactions I get the impression that the local controllers are unaware of the discrepancy at hand or maybe unaware of the exact verbiage on the departure plate. What further piques my interest in this issue is a secondary interaction I have had numerous times with the ind controllers. Often; even when all equipment is operable; tower will repeat an assigned heading during initial climb out; and well before the ifvj 2.3 DME. It seems the intent in this case is to depart from the MAREO2 departure language and turn prior to the 2.3 DME. However; I am unclear on what ATC's expectations are.I would like to know if I am correct in not accepting this departure if the DME is OTS. I would also like to better understand what should occur in the following situation: cleared via MAREO2; all equipment operable; tower clearance of; 'cleared for takeoff runway 23L; fly heading 210' (at this point I'm following the clearance to fly runway heading to ifvj 2.3 then turning to 210). Once airborne cleared by tower to (turn left heading 210; contact departure). Final suggestion: share report with ATC for feedback and possible follow up with ind ATC. I don't believe they should issue the clearance for this departure; or similar ones; if the equipment it is predicated on is inoperative.

Google
 

Original NASA ASRS Text

Title: Pilot reports of issue where DME that is OTS is still being used for clearances he is receiving out of IND airport.

Narrative: We were cleared for the MAREO2 departure and assigned Runway 23L for departure. The ILS 23L DME was NOTAMed out of service (IFVJ). For departure off 23L the MAREO2 departure reads; 'Climb on heading 227 to IFVJ 2.3 DME then on assigned heading 210; 227; or 242.' Without an operable IFVJ DME you can not comply with the departure. The reason that I point this out is that the DME for 23L and other IND runways is periodically NOTAMed out of service. Whenever this happens IND Clearance still issues clearances that are predicated on these items being operable. In these cases I will notify either Ground Control or Clearance Delivery that we are unable the departure. From those interactions I get the impression that the Local controllers are unaware of the discrepancy at hand or maybe unaware of the exact verbiage on the departure plate. What further piques my interest in this issue is a secondary interaction I have had numerous times with the IND controllers. Often; even when all equipment is operable; Tower will repeat an assigned heading during initial climb out; and well before the IFVJ 2.3 DME. It seems the intent in this case is to depart from the MAREO2 departure language and turn prior to the 2.3 DME. However; I am unclear on what ATC's expectations are.I would like to know if I am correct in not accepting this departure if the DME is OTS. I would also like to better understand what should occur in the following situation: Cleared via MAREO2; all equipment operable; Tower clearance of; 'Cleared for takeoff Runway 23L; fly heading 210' (At this point I'm following the clearance to fly runway heading to IFVJ 2.3 then turning to 210). Once airborne cleared by Tower to (turn left heading 210; contact Departure). Final suggestion: Share report with ATC for feedback and possible follow up with IND ATC. I don't believe they should issue the clearance for this departure; or similar ones; if the equipment it is predicated on is inoperative.

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