Welcome, Guest. Please login or register.
Did you miss your activation email?
April 20, 2014, 10:13:53 AM
Home Help Login Register      
News: LiveATC.net Flyers Released!  Please click here to download & print a copy and be sure to post at an airport near you!


+  LiveATC Discussion Forums
|-+  Air Traffic Monitoring
| |-+  Aviation Audio Clips (Moderators: dave, RonR)
| | |-+  Small Mistake on My Part
« previous next »
Pages: [1] 2 3 Go Down Print
Author Topic: Small Mistake on My Part  (Read 17786 times)
bcrosby
Sr. Member
****
Offline Offline

Posts: 332



WWW
« on: March 27, 2008, 01:58:47 PM »

Went on a x-country flight last night, on the way back I mistook runway 15 for 33..

I realized the mistake 0.5 seconds before tower called up asking if I had the airport in sight. I did, but was already on a right downwind for 15.. whoops.
« Last Edit: March 27, 2008, 02:00:49 PM by bcrosby » Logged

WhatAirspace
Newbie
*
Offline Offline

Posts: 5


« Reply #1 on: March 27, 2008, 03:57:15 PM »

Eh, I've seen it happen to experienced pilots, even saw a PC-12 do it a month or so ago.

Not to nitpick, but one thing I noticed is that you never really readback clearences, just your callsign.  Reading back everyting is a good way to encourage situational awareness for you, the controllers, and other pilots.  Some controllers I deal with will reapeat the clearence until you read back everything.  Granted, if the airspace is busy enough I limit my time on the air, but I at least readback pattern entry instructions and landing clearences.

I can't quote the AIM or anything, but that's just my $.02
Logged
bcrosby
Sr. Member
****
Offline Offline

Posts: 332



WWW
« Reply #2 on: March 27, 2008, 04:00:14 PM »

Technically, on VFR flights, you only need to readback hold short instructions and altitude restrictions.

Buttonville is a pretty busy airport, and there have been times when the controllers would announce to "all vfr aircraft" that full read backs are not required (when its busy).

I was taught (by all three of my instructors) to only acknowledge by using my call sign and to not read back everything.
Logged

KSYR-pjr
Hero Member
*****
Offline Offline

Posts: 1722



« Reply #3 on: March 27, 2008, 09:55:41 PM »

Technically, on VFR flights, you only need to readback hold short instructions and altitude restrictions.

Sorry to add, but since this is coming up I have an opinion to share, too.  There's the right way and there's the safe way and sometimes the two aren't necessarily the same.

As you know, reading back headings, landing clearances with runway numbers, and altimeter settings often times reinforces what you just heard and allows your short term memory to retain the information better.   This also, as pointed out earlier, provides additional situational awareness to the other pilots and controller on the frequency and potentially could expose a mistake by the controller or pilot before it becomes a problem (and thus, breaking the accident chain).

Consider this:  There was an accident several years ago here in the States where two Cessnas were waiting at the approach end for departure when another taxied up to an intersection on the opposite side of the runway, about 1,000 feet down the from the approach end.   The controller cleared the Cessna at the end of the runway for takeoff.  Just then the Cessna pilot at the intersection called "ready in sequence, Cessna XXX."  No location, no runway number, nothing else in his call-up.  The controller, thinking this was the pilot at the approach end, instructed him into position and hold, which he did.  Seconds later, the Cessna 150 rolling for takeoff came up from behind and slammed into his aircraft, killing all four aboard both aircraft.  Actually I think the pilot in aircraft on the takeoff roll saw the Cessna in position and attempted to takeoff early, then stalled the aircraft right on top of the one holding.

The point here is that if the pilot at the intersection included the verbiage that he was at the intersection, it would have most likely broke the chain of events that caused this accident since the controller would have known immediately who made that call.

Edit:  Oh, and often the problem with instructors is that a lot of them tend to be time builders looking to get into a commercial airline right seat and have very little real weather, unfamiliar airport, cross country flying experience outside of instructing.  Additionally, sometimes the information they pass down to their students has no roots in this kind of valuable experience. 

« Last Edit: March 27, 2008, 10:02:10 PM by KSYR-pjr » Logged

Regards, Peter
ATC Feed:  Syracuse (KSYR), NY
mk
Jr. Member
**
Offline Offline

Posts: 94



« Reply #4 on: March 27, 2008, 10:41:10 PM »

there is actually no requirement if you are IFR to read back any instructions if you want to cute and come up with excuses about not reading back clearences/instructions.  But what's your real excuse?  i hear an airline pilot do it now and again b/c it's gettin crazy on the freq, or b/c it's super slow.  the only clearence/instruction that is required to be read back that i'm aware of is hold short clearences, and i don't get to use that in the tracon.  KSYR-pjr is right, reading back all instructions is the BEST practice b/c it reaffirms to the controller that you might not just be one of those single engine bug smasher going for a sunday buzz to catch a glimpse and some big jets.

aviation is not the place to be taking short cuts, esp when it comes to your safety or mine.
Logged
bcrosby
Sr. Member
****
Offline Offline

Posts: 332



WWW
« Reply #5 on: March 27, 2008, 10:56:24 PM »

I agree that reading back instructions/clearances will help with retaining items in short term memory.

FYI, for reference CAR 602.31 outlines requirements in Canada for read backs, specifically:

602.31 (1) Subject to subsection (3), the pilot-in command of an aircraft shall

(a) comply with and acknowledge, to the appropriate air traffic control unit, all of the air traffic control instructions directed to and received by the pilot-in-command; and

(b) comply with all of the air traffic control clearances received and accepted by the pilot-in-command and

(i) subject to subsection (2), in the case of an IFR flight, read back to the appropriate air traffic control unit the text of any air traffic control clearance received, and

(ii) in the case of a VFR flight, read back to the appropriate air traffic control unit the text of any air traffic control clearance received, when so requested by the air traffic control unit.

So yes, you must read back clearances in an IFR flight.
Logged

jahulian
Newbie
*
Offline Offline

Posts: 9


« Reply #6 on: March 28, 2008, 11:20:23 PM »

It depends on the airport mostly, I think.  I know that at Montreal airport, there's a mandatory readback of the SIDs on clearance delivery.  There's a message on the ATIS and the clearance controllers are really strict about that.  I find it really annoying people who will just say : Alfa bravo charlie roger.  The controller doesn't know if you understood everything, you might be missing some stuff and other people on the frequency might not have caught what you said.  The only thing I don't read back is the wind and simple instructions on less busy frequencies.
Logged
mk
Jr. Member
**
Offline Offline

Posts: 94



« Reply #7 on: March 29, 2008, 10:15:24 AM »

my mistake...not familiar with the CARs
Logged
YWGTower
Newbie
*
Offline Offline

Posts: 29


« Reply #8 on: March 30, 2008, 11:32:23 PM »

That was a pretty dumb-assed mistake!
Logged
Jason
Hero Member
*****
Offline Offline

Posts: 1260


CFI/CFII


« Reply #9 on: March 30, 2008, 11:55:53 PM »

That was a pretty dumb-assed mistake!

Just like the one you made by hitting the "reply" and "post" buttons?  Please try to contribute something positive on these forums.  Negativity is key to losing members.
Logged
KSYR-pjr
Hero Member
*****
Offline Offline

Posts: 1722



« Reply #10 on: March 31, 2008, 11:16:57 AM »

That was a pretty dumb-assed mistake!

Just about all pilots and controllers make mistakes throughout their career- just this morning I heard a jetBlue pilot on frequency make one, so no one is immune.

Most who DO don't laugh; instead we empathize and recall those times when we were less than perfect.
Logged

Regards, Peter
ATC Feed:  Syracuse (KSYR), NY
bcrosby
Sr. Member
****
Offline Offline

Posts: 332



WWW
« Reply #11 on: March 31, 2008, 02:38:51 PM »

Ever since this post, I've been reading back instructions, even though they are not technically needed.

Just this past week on a short flight from YKZ to YSN I was sure to read back instructions from the terminal controller Cheesy

Logged

Casper87
Full Member
***
Offline Offline

Posts: 135


« Reply #12 on: April 01, 2008, 05:40:54 AM »

Quote
"The point here is that if the pilot at the intersection included the verbiage that he was at the intersection, it would have most likely broke the chain of events that caused this accident since the controller would have known immediately who made that call."

I appreciate the opinion but I dont  think that is the point. Yes, it would have helped if the pilot had stated the intersection. Granted people make mistakes, but if the controller doesnt know where the aircraft under his/her responsibility are....is that person in the right job?
On an aerodrome with ATC it is the controllers responsibility to ensure safe seperation.
Logged
KSYR-pjr
Hero Member
*****
Offline Offline

Posts: 1722



« Reply #13 on: April 01, 2008, 07:31:42 AM »

Yes, it would have helped if the pilot had stated the intersection. Granted people make mistakes, but if the controller doesnt know where the aircraft under his/her responsibility are....is that person in the right job?
On an aerodrome with ATC it is the controllers responsibility to ensure safe seperation.

The point here is that a pilot should use every tactic in his/her arsenal, including reading back instructions, to break the chain of events that lead to an accident.  Reading back instructions could very well be that one moment that snaps either the pilot or controller back to the entire picture of the unfolding situation.

Whether a person is right for a controller's position is irrelevant in this discussion since controllers are human and, like pilots, do occasionally make mistakes.   Additionally, a pilot erring can lead to a controller erring.  However, when a controller makes a mistake managing traffic it is the pilot and his/her passengers who have a much higher probability of dying.  When the deck is stacked in that manner, you better believe that going beyond the FARs (US regulations) and AIM (US aviation information manual) is the prudent action to take.
Logged

Regards, Peter
ATC Feed:  Syracuse (KSYR), NY
mhawke
Full Member
***
Offline Offline

Posts: 106


« Reply #14 on: April 01, 2008, 08:22:11 AM »

I'm neither a pilot or controller, just someone who enjoys flying and does it quite often for business.

However, I am the operations manager for a large chemical company and have worked in the Nuclear Power Industry.  Industries, which similar to aviation have a dedication to safety and operational discipline including the use of procedures because the risks are too high.

Too that end, I have to agree with KSYR-pjr, read backs are imperative.  In the nuclear power industry (especially in the engine room of a Nuclear Powered Submarine), all orders are read back.  There are two reasons for that, which have already been touched on.  They verify the understanding of the order by the person who is going to perform it, and it allows the person giving the order a chance to hear it rather then say it.  that provides an opportunity for that person's brain to process the order rather then give it, allowing a chance to verify that it is really what they wanted to do.

In the operations of large chemical plants we follow the same mantra.  In fact, out automated control systems follow it in a way, because the control system will verify key changes by repeating back setpoint changes and asking for an okay.  The number of incidents prevented by that sequence cannot even be counted.
Logged
Pages: [1] 2 3 Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!