37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 218500 |
Time | |
Date | 199208 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dnn |
State Reference | GA |
Altitude | msl bound lower : 6000 msl bound upper : 6000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : cha |
Operator | general aviation : corporate |
Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng |
Navigation In Use | Other |
Flight Phase | descent other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 150 flight time total : 2500 flight time type : 260 |
ASRS Report | 218500 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : cfi pilot : commercial |
Experience | flight time total : 1700 |
Events | |
Anomaly | non adherence : clearance non adherence : far |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After working south around a line of thunderstorms (which took extraordinary time), we were cleared when able direct to dalton, GA. I commanded the LORAN to do the same. Then upon establishing visual contact with the airport, I advised we had the airport in sight for the visual, and we were cleared for the approach, and told to cancel in air or on the ground through the rco. During downwind to base leg the ceo of the company advised we proceed on to calhoun, GA (6 mins southeast), our ultimate destination, because of the storm delay that we were short of time. I asked our copilot (new, rental pilot, second time in cockpit) to cancel IFR on the rco frequency on her #2 communication. She did, but apparently either failed to switch over to her #2 transmit position, or had the wrong frequency. There was apparently no acknowledgement. We were already at calhoun by this time, and I cancelled on the ground through FSS telling them we had attempted in the air and were not sure we were successful. They acknowledged our cancellation. Then cha approach calls saying we failed to cancel, they had blocked airspace and hadn't received anything over the rco. My failure appears to have been in not verifying the copilot's correct use of the #2 communication, whether it was the communication select switch or the frequency incorrectly set. Plus she did not indicate to me that she had not received acknowledgement on our cancellation until I questioned her on the ground. I should have verified this in the air. I was busy flying the plane working around the buildups that were around the plane, and left the work to her since she is a cfii/mei with 1700+ hours.
Original NASA ASRS Text
Title: CORP ACFT FAILS TO ASSURE CANCELLATION OF IFR FLT PLAN WHEN CEO CHANGES DEST.
Narrative: AFTER WORKING S AROUND A LINE OF TSTMS (WHICH TOOK EXTRAORDINARY TIME), WE WERE CLRED WHEN ABLE DIRECT TO DALTON, GA. I COMMANDED THE LORAN TO DO THE SAME. THEN UPON ESTABLISHING VISUAL CONTACT WITH THE ARPT, I ADVISED WE HAD THE ARPT IN SIGHT FOR THE VISUAL, AND WE WERE CLRED FOR THE APCH, AND TOLD TO CANCEL IN AIR OR ON THE GND THROUGH THE RCO. DURING DOWNWIND TO BASE LEG THE CEO OF THE COMPANY ADVISED WE PROCEED ON TO CALHOUN, GA (6 MINS SE), OUR ULTIMATE DEST, BECAUSE OF THE STORM DELAY THAT WE WERE SHORT OF TIME. I ASKED OUR COPLT (NEW, RENTAL PLT, SECOND TIME IN COCKPIT) TO CANCEL IFR ON THE RCO FREQ ON HER #2 COM. SHE DID, BUT APPARENTLY EITHER FAILED TO SWITCH OVER TO HER #2 XMIT POS, OR HAD THE WRONG FREQ. THERE WAS APPARENTLY NO ACKNOWLEDGEMENT. WE WERE ALREADY AT CALHOUN BY THIS TIME, AND I CANCELLED ON THE GND THROUGH FSS TELLING THEM WE HAD ATTEMPTED IN THE AIR AND WERE NOT SURE WE WERE SUCCESSFUL. THEY ACKNOWLEDGED OUR CANCELLATION. THEN CHA APCH CALLS SAYING WE FAILED TO CANCEL, THEY HAD BLOCKED AIRSPACE AND HADN'T RECEIVED ANYTHING OVER THE RCO. MY FAILURE APPEARS TO HAVE BEEN IN NOT VERIFYING THE COPLT'S CORRECT USE OF THE #2 COM, WHETHER IT WAS THE COM SELECT SWITCH OR THE FREQ INCORRECTLY SET. PLUS SHE DID NOT INDICATE TO ME THAT SHE HAD NOT RECEIVED ACKNOWLEDGEMENT ON OUR CANCELLATION UNTIL I QUESTIONED HER ON THE GND. I SHOULD HAVE VERIFIED THIS IN THE AIR. I WAS BUSY FLYING THE PLANE WORKING AROUND THE BUILDUPS THAT WERE AROUND THE PLANE, AND LEFT THE WORK TO HER SINCE SHE IS A CFII/MEI WITH 1700+ HRS.
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.