Narrative:

While being vectored into fty by atlanta approach we were vectored to sequence us behind a slower aircraft. As we were being switched from atlanta approach to fty tower and cleared for the visual runway 26 we were too close to the runway and too high to continue straight in so we turned out to a longer base and squared the turn to final. While being told to switch to 118.45; fty tower frequency; a drone was noticed passing below us and to the left. We made mention of it and now were a bit nervous and on extra high alert keeping an eye out for another that might be in the area. During this time we were also having to execute an accelerated approach (adding flaps and gear in a much more compressed time frame due to being closer than normal to the airport). When on short final (around 1 mile) and approximately 300 ft I looked at the radio and noticed tower frequency; 118.45 had been typed in but we had not switched over to it from atlanta approach. I quickly made it known to the other pilot and immediately switched and called tower. Tower cleared us to land and upon landing asked us to call the tower when we were done. I called the tower once our passengers had left and conveyed the entire story to him as well; explaining how the compressed timeframe and the spotting of a drone close to the airport led to being distracted and forgetting to switch until short final. This situation was caused by allowing extra distractions take focus away from the immediate issues at hand. The other pilot was flying so the accelerated approach was in his control and the drone siting had passed but I was distracted thinking about those things behind me instead of what was in front of me.

Google
 

Original NASA ASRS Text

Title: BE40 First Officer reported sighting a drone during a visual approach to FTY. Due to the distraction; switching to the Tower was overlooked until very short final.

Narrative: While being vectored into FTY by Atlanta Approach we were vectored to sequence us behind a slower aircraft. As we were being switched from Atlanta Approach to FTY Tower and cleared for the visual Runway 26 we were too close to the runway and too high to continue straight in so we turned out to a longer base and squared the turn to final. While being told to switch to 118.45; FTY Tower frequency; a drone was noticed passing below us and to the left. We made mention of it and now were a bit nervous and on extra high alert keeping an eye out for another that might be in the area. During this time we were also having to execute an accelerated approach (adding flaps and gear in a much more compressed time frame due to being closer than normal to the airport). When on short final (around 1 mile) and approximately 300 ft I looked at the radio and noticed tower frequency; 118.45 had been typed in but we had not switched over to it from Atlanta Approach. I quickly made it known to the other pilot and immediately switched and called tower. Tower cleared us to land and upon landing asked us to call the tower when we were done. I called the tower once our passengers had left and conveyed the entire story to him as well; explaining how the compressed timeframe and the spotting of a drone close to the airport led to being distracted and forgetting to switch until short final. This situation was caused by allowing extra distractions take focus away from the immediate issues at hand. The other pilot was flying so the accelerated approach was in his control and the drone siting had passed but I was distracted thinking about those things behind me instead of what was in front of me.

Data retrieved from NASA's ASRS site 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.