Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Flight Crew Last 90 Days 100; Flight Crew Total 8400; Flight Crew Type 2000
Communication Breakdown; Situational Awareness
Conflict NMAC; Deviation / Discrepancy - Procedural Other / Unknown
General None Reported / Taken
Environment - Non Weather Related; Procedure; Airport
The single engine aircraft was approaching HPN from the north and was instructed to join a right downwind for Runway 34. That aircraft made a midfield right downwind call and Tower acknowledged the single's position in a traffic call to another aircraft. HPN Tower cleared the single to land and added 'keep it tight.' Tower clears an aircraft for takeoff on Runway 11 and calls his traffic as an aircraft east but doesn't mention the single that's now turning final. After crossing the threshold of Runway 34 and waiting for a radio transmission to end; I key the mike and say 'Tower is that guy rolling on 11.' At this point I'm not sure which aircraft will arrive at the intersection first and if the twin will be airborne or not. As I release the push to talk button I hear '… continue.' The single lands on [Runway] 34 about 400 FT before the runway intersection as the twin crosses it about 20 FT in the air. The single exits [Runway] 34 at Foxtrot. While listening to the Tower audio; I learned that HPN Tower had 'stepped on' the end of my transmission with a 'go-around; go-around' call. This was never heard in the single engine aircraft because the push-to-talk button was still depressed. I frankly think that the Tower had forgotten about the single. This may be evidenced by the absence of the single's position in the traffic report for the departing twin. Additionally; the single pilot was not told an aircraft would be departing Runway 11.
A pilot at HPN reported a Near Miss between a single engine aircraft landing Runway 34 and light twin taking off on Runway 11.