37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 480900 |
Time | |
Date | 200008 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sjc.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : sjc.tower tower : dfw.tower |
Operator | general aviation : instructional |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : takeoff roll |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | tower : sjc.tower |
Operator | general aviation : personal |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | landing : go around |
Person 1 | |
Affiliation | other |
Function | instruction : instructor oversight : pic |
Qualification | pilot : commercial pilot : instrument pilot : cfi |
Experience | flight time total : 260 |
ASRS Report | 480900 |
Person 2 | |
Affiliation | other |
Function | instruction : trainee |
Qualification | pilot : student |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : clearance non adherence : published procedure other anomaly other |
Independent Detector | other controllerb |
Resolutory Action | controller : issued advisory controller : issued new clearance flight crew : executed go around |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This particular flight up until the moment of 'conflict' was uneventful. This training flight began with 1 hour of ground instruction. A normal preflight was done as well as normal taxi to run-up. As I recall, the radio frequency 121.7 (ground) was not congested. My student (pre-private) was making all radio calls with my supervision. Taxi from runway 29 run-up across taxiway V was uneventful. Ground instructed my student to contact tower 120.7 -- he did. When holding short of runway 29, I recall several traffic callouts for both runways (29 and 30) -- one of which was a piston single (don't recall what make/model) on final whose landing light I believe I saw but could not make out the aircraft. Another call told us (from tower) that we would have to hold in position for a 'departing' or 'arriving' (not sure) heavy -- 'xyz we are going to have you hold short there for about 2 more mins for....' the next call I remember was a clearance (or what I and my student believed to be a clearance) to take off on runway 29 -- and to expedite. My student called back to tower 'cessna xyz cleared for takeoff, runway 29, expediting.' I thought that tower was going to try to get us out before the wake turbulence problem, and before our traffic on final. My student was going through normal procedures before takeoff lights (strobes and landing) came on (transponder to altitude) and on centerline (several seconds later), went to actions -- power to full. Then we received a call -- xyz, uhhh, disregard, a call was made to the aircraft on final to go around and us xyz to stop. We were, only then, told that the clearance we answered was meant to an MD80 on the parallel. I thought tower was supposed to correct any incorrect clearance readbacks. If not, why not?
Original NASA ASRS Text
Title: INSTRUCTIONAL FLC TAKES CLRNC FOR TKOF ISSUED TO MD80. TWR MISSES THE INCORRECT READBACK. AN ABORTED TKOF AND A GAR ARE THE RESULT.
Narrative: THIS PARTICULAR FLT UP UNTIL THE MOMENT OF 'CONFLICT' WAS UNEVENTFUL. THIS TRAINING FLT BEGAN WITH 1 HR OF GND INSTRUCTION. A NORMAL PREFLT WAS DONE AS WELL AS NORMAL TAXI TO RUN-UP. AS I RECALL, THE RADIO FREQ 121.7 (GND) WAS NOT CONGESTED. MY STUDENT (PRE-PVT) WAS MAKING ALL RADIO CALLS WITH MY SUPERVISION. TAXI FROM RWY 29 RUN-UP ACROSS TXWY V WAS UNEVENTFUL. GND INSTRUCTED MY STUDENT TO CONTACT TWR 120.7 -- HE DID. WHEN HOLDING SHORT OF RWY 29, I RECALL SEVERAL TFC CALLOUTS FOR BOTH RWYS (29 AND 30) -- ONE OF WHICH WAS A PISTON SINGLE (DON'T RECALL WHAT MAKE/MODEL) ON FINAL WHOSE LNDG LIGHT I BELIEVE I SAW BUT COULD NOT MAKE OUT THE ACFT. ANOTHER CALL TOLD US (FROM TWR) THAT WE WOULD HAVE TO HOLD IN POS FOR A 'DEPARTING' OR 'ARRIVING' (NOT SURE) HVY -- 'XYZ WE ARE GOING TO HAVE YOU HOLD SHORT THERE FOR ABOUT 2 MORE MINS FOR....' THE NEXT CALL I REMEMBER WAS A CLRNC (OR WHAT I AND MY STUDENT BELIEVED TO BE A CLRNC) TO TAKE OFF ON RWY 29 -- AND TO EXPEDITE. MY STUDENT CALLED BACK TO TWR 'CESSNA XYZ CLRED FOR TKOF, RWY 29, EXPEDITING.' I THOUGHT THAT TWR WAS GOING TO TRY TO GET US OUT BEFORE THE WAKE TURB PROB, AND BEFORE OUR TFC ON FINAL. MY STUDENT WAS GOING THROUGH NORMAL PROCS BEFORE TKOF LIGHTS (STROBES AND LNDG) CAME ON (XPONDER TO ALT) AND ON CTRLINE (SEVERAL SECONDS LATER), WENT TO ACTIONS -- PWR TO FULL. THEN WE RECEIVED A CALL -- XYZ, UHHH, DISREGARD, A CALL WAS MADE TO THE ACFT ON FINAL TO GO AROUND AND US XYZ TO STOP. WE WERE, ONLY THEN, TOLD THAT THE CLRNC WE ANSWERED WAS MEANT TO AN MD80 ON THE PARALLEL. I THOUGHT TWR WAS SUPPOSED TO CORRECT ANY INCORRECT CLRNC READBACKS. IF NOT, WHY NOT?
Data retrieved from NASA's ASRS site as of July 2007 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.