37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 297242 |
Time | |
Date | 199501 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : pit |
State Reference | PA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : holding |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain instruction : instructor oversight : pic |
Qualification | pilot : atp |
Experience | flight time total : 11000 |
ASRS Report | 297242 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | non adherence : far non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | other other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While cleared into position to hold on runway 28R at pit, tower said there would be a 'short delay' in position. My first officer was new to the aircraft and I was the instructor pilot giving him his IOE. This was leg #3 of his actual flying. After tower cleared us into position, the first officer must have mistakenly switched to departure control. We were not aware of this error until I noticed an ACARS message from company to check frequency 128.3. I immediately realized we were on departure control and switched to tower of 128.3. I apologized to tower and told him we had mistakenly been on departure. There was no conflict of traffic and no gars to our knowledge. Takeoff was then normal. Upon landing again 2 hours later at pit, I called the tower supervisor. He said there was no conflict and he appreciated me calling. Callback conversation with reporter revealed the following information: the reporter flies the B-737-200 for a major united states air carrier. The pit ATCT had no traffic problems because of this incident.
Original NASA ASRS Text
Title: AN ACR MLG FO SET IN THE WRONG RADIO FREQ CAUSING A TKOF DELAY.
Narrative: WHILE CLRED INTO POS TO HOLD ON RWY 28R AT PIT, TWR SAID THERE WOULD BE A 'SHORT DELAY' IN POS. MY FO WAS NEW TO THE ACFT AND I WAS THE INSTRUCTOR PLT GIVING HIM HIS IOE. THIS WAS LEG #3 OF HIS ACTUAL FLYING. AFTER TWR CLRED US INTO POS, THE FO MUST HAVE MISTAKENLY SWITCHED TO DEP CTL. WE WERE NOT AWARE OF THIS ERROR UNTIL I NOTICED AN ACARS MESSAGE FROM COMPANY TO CHK FREQ 128.3. I IMMEDIATELY REALIZED WE WERE ON DEP CTL AND SWITCHED TO TWR OF 128.3. I APOLOGIZED TO TWR AND TOLD HIM WE HAD MISTAKENLY BEEN ON DEP. THERE WAS NO CONFLICT OF TFC AND NO GARS TO OUR KNOWLEDGE. TKOF WAS THEN NORMAL. UPON LNDG AGAIN 2 HRS LATER AT PIT, I CALLED THE TWR SUPVR. HE SAID THERE WAS NO CONFLICT AND HE APPRECIATED ME CALLING. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR FLIES THE B-737-200 FOR A MAJOR UNITED STATES ACR. THE PIT ATCT HAD NO TFC PROBS BECAUSE OF THIS INCIDENT.
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.