Narrative:

Aircraft was cleared for visual approach runway 27L at ptk by detroit approach. Previously airspeed assigned was 180 KTS, altitude 3000 ft MSL. As we contacted ptk tower, they instructed us to follow a MU300 diamond jet on a 3 NM final to runway 27L. The traffic patterns to both runway 27L/27R (was) were saturated. (Turbine and light GA aircraft) the ptk tower controller was working both runways, multiple aircraft. When we picked up the diamond jet, the first officer (flying pilot) called for 'gear down, landing checklist.' aircraft was still on the downwind leg. At that instant, I saw a (piper) cherokee climbing into us, on a direct intercept. There was only enough time to call 'oh my god, traffic.' the first officer sensed the urgency in my voice and took immediate evasive action. (Go around power pitch 15 degrees) the first officer stated that he saw the conflicting cherokee at approximately the time I called out.horizontal miss distance O ft. Verticle miss distance less than 100 ft. I immediately informed the tower of the conflict. The controller responded that he did not tell us about traffic, because there was no conflict!! I instructed the first officer to re-configure for landing, and turn base to final. The tower controller then created yet another conflict by assigning runway 27R, with multiple GA light aircraft in right traffic. We were then cleared to lnd on runway 27L, frequency congestion was so bad that the acknowledgement of landing clearance was never responded to by tower controller. By this point we were on a 2 1/2 mi final for runway 27L. The tower controller was ordering us to 'fly as fast as possible,' because there was a merlin (sa-227) 1 mi in trail. Our airspeed was 140 KTS (vref + 40 KTS) merlin (sa-227) airspeed 180 KTS plus!! The final conflict occurred on a 1 mi final, when tower controller cleared a mooney to fly over short final for runway 27L to join left base for 27R. The mooney passed 200 ft overhead. Pontiac tower needs to have a safety audit as soon as possible! I have personally had many conflicts, on VFR days. All of these conflicts are a result of poor tower oversight. There is going to be a catastrophic mid-air collision at pontiac, mi (ptk). Traffic should be restricted to turbine aircraft only during the hours of 2OOO zulu-2300 zulu. On runway 27L, with airspeed restricted to 170 KTS, with traffic vectored on to localizer back course runway 27L at ernst outer marker, with specific arrival tracks. Light GA aircraft should be restricted to runway 27R, with entry track beginning at pontiac VOR, with separate tower control runway 27R. Callback conversation with reporter revealed the following information: reporter stated that he did not file an near midair collision report since his company did not want to 'make waves...' he cited other transgressions allowed by the tower controller that of allowing taxi and flight operations during fog conditions where visibility was near zero.

Google
 

Original NASA ASRS Text

Title: A BE-300 CORPORATE PIC RPT ON TWO NMACS AND ALLEGED CONFUSION WITH TFC MIX ON TWO PARALLEL RWYS WITH ONLY ONE CTLR THAT WAS OVERLOADED BY TFC VOLUME AT PTK.

Narrative: ACFT WAS CLRED FOR VISUAL APCH RWY 27L AT PTK BY DETROIT APCH. PREVIOUSLY AIRSPEED ASSIGNED WAS 180 KTS, ALT 3000 FT MSL. AS WE CONTACTED PTK TWR, THEY INSTRUCTED US TO FOLLOW A MU300 DIAMOND JET ON A 3 NM FINAL TO RWY 27L. THE TFC PATTERNS TO BOTH RWY 27L/27R (WAS) WERE SATURATED. (TURBINE AND LIGHT GA ACFT) THE PTK TWR CTLR WAS WORKING BOTH RWYS, MULTIPLE ACFT. WHEN WE PICKED UP THE DIAMOND JET, THE FO (FLYING PLT) CALLED FOR 'GEAR DOWN, LNDG CHKLIST.' ACFT WAS STILL ON THE DOWNWIND LEG. AT THAT INSTANT, I SAW A (PIPER) CHEROKEE CLBING INTO US, ON A DIRECT INTERCEPT. THERE WAS ONLY ENOUGH TIME TO CALL 'OH MY GOD, TFC.' THE FO SENSED THE URGENCY IN MY VOICE AND TOOK IMMEDIATE EVASIVE ACTION. (GAR PWR PITCH 15 DEGREES) THE FO STATED THAT HE SAW THE CONFLICTING CHEROKEE AT APPROX THE TIME I CALLED OUT.HORIZONTAL MISS DISTANCE O FT. VERTICLE MISS DISTANCE LESS THAN 100 FT. I IMMEDIATELY INFORMED THE TWR OF THE CONFLICT. THE CTLR RESPONDED THAT HE DID NOT TELL US ABOUT TFC, BECAUSE THERE WAS NO CONFLICT!! I INSTRUCTED THE FO TO RE-CONFIGURE FOR LNDG, AND TURN BASE TO FINAL. THE TWR CTLR THEN CREATED YET ANOTHER CONFLICT BY ASSIGNING RWY 27R, WITH MULTIPLE GA LIGHT ACFT IN R TFC. WE WERE THEN CLRED TO LND ON RWY 27L, FREQ CONGESTION WAS SO BAD THAT THE ACKNOWLEDGEMENT OF LNDG CLRNC WAS NEVER RESPONDED TO BY TWR CTLR. BY THIS POINT WE WERE ON A 2 1/2 MI FINAL FOR RWY 27L. THE TWR CTLR WAS ORDERING US TO 'FLY AS FAST AS POSSIBLE,' BECAUSE THERE WAS A MERLIN (SA-227) 1 MI IN TRAIL. OUR AIRSPEED WAS 140 KTS (VREF + 40 KTS) MERLIN (SA-227) AIRSPEED 180 KTS PLUS!! THE FINAL CONFLICT OCCURRED ON A 1 MI FINAL, WHEN TWR CTLR CLRED A MOONEY TO FLY OVER SHORT FINAL FOR RWY 27L TO JOIN L BASE FOR 27R. THE MOONEY PASSED 200 FT OVERHEAD. PONTIAC TWR NEEDS TO HAVE A SAFETY AUDIT ASAP! I HAVE PERSONALLY HAD MANY CONFLICTS, ON VFR DAYS. ALL OF THESE CONFLICTS ARE A RESULT OF POOR TWR OVERSIGHT. THERE IS GOING TO BE A CATASTROPHIC MID-AIR COLLISION AT PONTIAC, MI (PTK). TFC SHOULD BE RESTRICTED TO TURBINE ACFT ONLY DURING THE HRS OF 2OOO ZULU-2300 ZULU. ON RWY 27L, WITH AIRSPEED RESTRICTED TO 170 KTS, WITH TFC VECTORED ON TO LOC BC RWY 27L AT ERNST OUTER MARKER, WITH SPECIFIC ARR TRACKS. LIGHT GA ACFT SHOULD BE RESTRICTED TO RWY 27R, WITH ENTRY TRACK BEGINNING AT PONTIAC VOR, WITH SEPARATE TWR CTL RWY 27R. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT HE DID NOT FILE AN NMAC RPT SINCE HIS COMPANY DID NOT WANT TO 'MAKE WAVES...' HE CITED OTHER TRANSGRESSIONS ALLOWED BY THE TWR CTLR THAT OF ALLOWING TAXI AND FLT OPS DURING FOG CONDITIONS WHERE VIS WAS NEAR ZERO.

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.