Return to Answer

The topic is as relevant as it was when it was initially posted. So some notes:

• I'd say missing an ATC directed turn off the runway, after a correct and confirmed readback, could be a violation, but clearly, this wasn't the case. So no violation, and no intended violation of procedure, but there certainly was an error as you point out yourself.

• In the first place, the Tower gives such modifier instructions as a result of the perception of an arising risk. Maybe be an airplane landing behind you, could be an airplane likely to cross your likely exit, or worse, your mandatory RWY exit. It could be an understanding between Controllers and Pilots at a local for convenience rather than purely Safety. You may not be aware of this last, depending on your experience, familiarity with the airfield and local procedures and conventions.
  A few points come up:

• in case of a readback/switchover situation, logic dictates that you need to give it a reasonable time on frequency, incase your readback has to be corrected, before switching frequencies. We get rushed sometimes due to a clash of procedures ("change to GND point Niner for further") and we are unable or it is impossible to prioritize.

• Conversely when you change over frequency, good R/T practice requires a small pause before using the ptt to ensure you don't 'step on' someone else's transmission (Who knows, could be a readback or it's acknowledgement).

• an error, though it may not be a violation, may still need discussion, so as to come up with an understanding of what happened, why it happened and how we can help avoiding or eliminate such occurrences.

• As Pilot in Command, certain Controller instructions may not be acceptable to you. You may exercise your command authority, for the safety of the airplane, persons affected, and goods and property etc., but remember, you invariably must be able to defend your actions and decisions as being the safest course of action based on the info available to you and the realtime situation.

• Seems Tower did the needful by contacting you via Ground freq. We pilots tend to (naturally) obsess about such occurrences, and the bogie of violations and consequences come more readily to mind, somewhat repressing a genuine concern for addressing the circumstances.

• BTW, what did the Tower guys have to say to you in the end?

The topic is as relevant as it was when it was initially posted. So some notes:

ICAO Annexe 10 extract para 5.2.1.9.2.2 PANS.

An aircraft station should acknowledge receipt of important air traffic control messages or parts thereof by reading them back and terminating the readback by its radio call sign.

Note 1.— Air traffic control clearances, instructions and information requiring readback are specified in PANS-ATM (Doc 4444).

Note 2.— The following example illustrates the application of this procedure:

(ATC clearance by network station to an aircraft)

Station: TWA NINE SIX THREE MADRID

Aircraft: MADRID TWA NINE SIX THREE

Station: TWA NINE SIX THREE MADRID — ATC CLEARS TWA NINE SIX THREE TO DESCEND TO NINE THOUSAND FEET

Aircraft (acknowledging): CLEARED TO DESCEND TO NINE THOUSAND FEET — TWA NINE SIX THREE

Station (denoting accuracy of readback): MADRID

• I'd say missing an ATC directed turn off the runway, after a correct and confirmed readback, could be a violation, but clearly, this wasn't the case. So no violation, and no intended violation of procedure, but there certainly was an error as you point out yourself.

• In the first place, the Tower gives such modifier instructions as a result of the perception of an arising risk. Maybe be an airplane landing behind you, could be an airplane likely to cross your likely exit, or worse, your mandatory RWY exit. It could be an understanding between Controllers and Pilots at a local for convenience rather than purely Safety. You may not be aware of this last, depending on your experience, familiarity with the airfield and local procedures and conventions.
  A few points come up:

• in case of a readback/switchover situation, logic dictates that you need to give it a reasonable time on frequency, incase your readback has to be corrected, before switching frequencies. We get rushed sometimes due to a clash of procedures ("change to GND point Niner for further") and we are unable or it is impossible to prioritize.

• Conversely when you change over frequency, good R/T practice requires a small pause before using the ptt to ensure you don't 'step on' someone else's transmission (Who knows, could be a readback or it's acknowledgement).

• an error, though it may not be a violation, may still need discussion, so as to come up with an understanding of what happened, why it happened and how we can help avoiding or eliminate such occurrences.

• As Pilot in Command, certain Controller instructions may not be acceptable to you. You may exercise your command authority, for the safety of the airplane, persons affected, and goods and property etc., but remember, you invariably must be able to defend your actions and decisions as being the safest course of action based on the info available to you and the realtime situation.

• Seems Tower did the needful by contacting you via Ground freq. We pilots tend to (naturally) obsess about such occurrences, and the bogie of violations and consequences come more readily to mind, somewhat repressing a genuine concern for addressing the circumstances.

• BTW, what did the Tower guys have to say to you in the end?

The topic is as relevant as it was when it was initially posted. So some notes:

(There may be implications due to the intro of datalink, datalink not discussed in this thread.)

• I'd say missing an ATC directed turn off the runway, after a correct and confirmed readback, could be a violation, but clearly, this wasn't the case. So no violation, and no intended violation of procedure, but there certainly was an error as you point out yourself.

• In the first place, the Tower gives such modifier instructions as a result of the perception of an arising risk. Maybe be an airplane landing behind you, could be an airplane likely to cross your likely exit, or worse, your mandatory RWY exit. It could be an understanding between Controllers and Pilots at a local for convenience rather than purely Safety. You may not be aware of this last, depending on your experience, familiarity with the airfield and local procedures and conventions.
  A few points come up:

• in case of a readback/switchover situation, logic dictates that you need to give it a reasonable time on frequency, incase your readback has to be corrected, before switching frequencies. We get rushed sometimes due to a clash of procedures ("change to GND point Niner for further") and we are unable or it is impossible to prioritize.

• Conversely when you change over frequency, good R/T practice requires a small pause before using the ptt to ensure you don't 'step on' someone else's transmission (Who knows, could be a readback or it's acknowledgement).

• an error, though it may not be a violation, may still need discussion, so as to come up with an understanding of what happened, why it happened and how we can help avoiding or eliminate such occurrences.

• As Pilot in Command, certain Controller instructions may not be acceptable to you. You may exercise your command authority, for the safety of the airplane, persons affected, and goods and property etc., but remember, you invariably must be able to defend your actions and decisions as being the safest course of action based on the info available to you and the realtime situation.

• Seems Tower did the needful by contacting you via Ground freq. We pilots tend to (naturally) obsess about such occurrences, and the bogie of violations and consequences come more readily to mind, somewhat repressing a genuine concern for addressing the circumstances.

• BTW, what did the Tower guys have to say to you in the end?

The topic is as relevant as it was when it was initially posted. So some notes:

• I'd say missing an ATC directed turn off the runway, after a correct and confirmed readback, could be a violation, but clearly, this wasn't the case. So no violation, and no intended violation of procedure, but there certainly was an error as you point out yourself.

• In the first place, the Tower gives such modifier instructions as a result of the perception of an arising risk. Maybe be an airplane landing behind you, could be an airplane likely to cross your likely exit, or worse, your mandatory RWY exit. It could be an understanding between Controllers and Pilots at a local for convenience rather than purely Safety. You may not be aware of this last, depending on your experience, familiarity with the airfield and local procedures and conventions.
  A few points come up:

• in case of a readback/switchover situation, logic dictates that you need to give it a reasonable time on frequency, incase your readback has to be corrected, before switching frequencies. We get rushed sometimes due to a clash of procedures ("change to GND point Niner for further") and we are unable or it is impossible to prioritize.

• Conversely when you change over frequency, good R/T practice requires a small pause before using the ptt to ensure you don't 'step on' someone else's transmission (Who knows, could be a readback or it's acknowledgement).

• an error, though it may not be a violation, may still need discussion, so as to come up with an understanding of what happened, why it happened and how we can help avoiding or eliminate such occurrences.

• As Pilot in Command, certain Controller instructions may not be acceptable to you. You may exercise your command authority, for the safety of the airplane, persons affected, and goods and property etc., but remember, you invariably must be able to defend your actions and decisions as being the safest course of action based on the info available to you and the realtime situation.

• Seems Tower did the needful by contacting you via Ground freq. We pilots tend to (naturally) obsess about such occurrences, and the bogie of violations and consequences come more readily to mind, somewhat repressing a genuine concern for addressing the circumstances.

• BTW, what did the Tower guys have to say to you in the end?

The topic is as relevant as it was when it was initially posted. So some notes:

(There may be implications due to the intro of datalink, datalink not discussed in this thread.)

• I'd say missing an ATC directed turn off the runway, after a correct and confirmed readback, could be a violation, but clearly, this wasn't the case. So no violation, and no intended violation of procedure, but there certainly was an error as you point out yourself.

• In the first place, the Tower gives such modifier instructions as a result of the perception of an arising risk. Maybe be an airplane landing behind you, could be an airplane likely to cross your likely exit, or worse, your mandatory RWY exit. It could be an understanding between Controllers and Pilots at a local for convenience rather than purely Safety. You may not be aware of this last, depending on your experience, familiarity with the airfield and local procedures and conventions.
  A few points come up:

• in case of a readback/switchover situation, logic dictates that you need to give it a reasonable time on frequency, incase your readback has to be corrected, before switching frequencies. We get rushed sometimes due to a clash of procedures ("change to GND point Niner for further") and we are unable or it is impossible to prioritize.

• Conversely when you change over frequency, good R/T practice requires a small pause before using the ptt to ensure you don't 'step on' someone else's transmission (Who knows, could be a readback or it's acknowledgement).

• an error, though it may not be a violation, may still need discussion, so as to come up with an understanding of what happened, why it happened and how we can help avoiding or eliminate such occurrences.

• As Pilot in Command, certain Controller instructions may not be acceptable to you. You may exercise your command authority, for the safety of the airplane, persons affected, and goods and property etc., but remember, you invariably must be able to defend your actions and decisions as being the safest course of action based on the info available to you and the realtime situation.

• Seems Tower did the needful by contacting you via Ground freq. We pilots tend to (naturally) obsess about such occurrences, and the bogie of violations and consequences come more readily to mind, somewhat repressing a genuine concern for addressing the circumstances.

• BTW, what did the Tower guys have to say to you in the end?

br
skipper

The topic is as relevant as it was when it was initially posted. So some notes:

(There may be implications due to the intro of datalink, datalink not discussed in this thread.)

• I'd say missing an ATC directed turn off the runway, after a correct and confirmed readback, could be a violation, but clearly, this wasn't the case. So no violation, and no intended violation of procedure, but there certainly was an error as you point out yourself.

• In the first place, the Tower gives such modifier instructions as a result of the perception of an arising risk. Maybe be an airplane landing behind you, could be an airplane likely to cross your likely exit, or worse, your mandatory RWY exit. It could be an understanding between Controllers and Pilots at a local for convenience rather than purely Safety. You may not be aware of this last, depending on your experience, familiarity with the airfield and local procedures and conventions.
  A few points come up:

• in case of a readback/switchover situation, logic dictates that you need to give it a reasonable time on frequency, incase your readback has to be corrected, before switching frequencies. We get rushed sometimes due to a clash of procedures ("change to GND point Niner for further") and we are unable or it is impossible to prioritize.

• Conversely when you change over frequency, good R/T practice requires a small pause before using the ptt to ensure you don't 'step on' someone else's transmission (Who knows, could be a readback or it's acknowledgement).

• an error, though it may not be a violation, may still need discussion, so as to come up with an understanding of what happened, why it happened and how we can help avoiding or eliminate such occurrences.

• As Pilot in Command, certain Controller instructions may not be acceptable to you. You may exercise your command authority, for the safety of the airplane, persons affected, and goods and property etc., but remember, you invariably must be able to defend your actions and decisions as being the safest course of action based on the info available to you and the realtime situation.

• Seems Tower did the needful by contacting you via Ground freq. We pilots tend to (naturally) obsess about such occurrences, and the bogie of violations and consequences come more readily to mind, somewhat repressing a genuine concern for addressing the circumstances.

• BTW, what did the Tower guys have to say to you in the end?