Narrative:

Land runway 7/2 intersecting runway operation; NOTAM out for phf stating taxiway 'G' closed; taxiway 'D' closed from taxiway 'G' to ILS critical area. Therefore; aircraft landing runway 7 have to back taxi if landing full length. A C172 called from the east requesting touch-and-gos. At this point I notice a string of aircraft inbound for phf. I stated to the C172 unable touch-and-gos; but can offer a full stop taxi back. [I] instructed the C172 to enter right down wind for runway 2. First plane was a citation and landed with no problem and turned off runway. I made a blanket broadcast reiterating the NOTAM taxiway closures. By then the C172 was a beam numbers runway 2; so he was issued runway 2 cleared for option with traffic; a LJ35 5M final. The LJ35 was then told about the C172 on a short right base for runway 2. The LJ35 reported cesena traffic in sight. Once the cessna was over the numbers; the LJ35 was on a half mile final and said that he was executing a missed approach. From all controllers' judgment in the tower; the cesena traffic would have been through the intersection long before the LJ35 crossed the threshold of runway 7. Recommendation: after the situation was resolved; the controller in charge found out that the approach control had no idea the tower had to back taxi. I recommend ids-4 equipment at the tower so that the tower may update it and keep approach aware of constant changes. If approach was aware of the closures; maybe they could have given more space between aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: PHF Controller described a go around event initiated by an aircraft on final for Runway 7 when observing traffic on a short right base for Runway 2; the reporter indicating appropriate intersection separation was maintained.

Narrative: Land Runway 7/2 intersecting runway operation; NOTAM out for PHF stating Taxiway 'G' closed; Taxiway 'D' closed from Taxiway 'G' to ILS critical area. Therefore; aircraft landing Runway 7 have to back taxi if landing full length. A C172 called from the east requesting touch-and-gos. At this point I notice a string of aircraft inbound for PHF. I stated to the C172 unable touch-and-gos; but can offer a full stop taxi back. [I] instructed the C172 to enter right down wind for Runway 2. First plane was a Citation and landed with no problem and turned off runway. I made a blanket broadcast reiterating the NOTAM TAXIWAY closures. By then the C172 was a beam numbers Runway 2; so he was issued Runway 2 cleared for option with traffic; a LJ35 5M final. The LJ35 was then told about the C172 on a short right base for Runway 2. The LJ35 reported Cesena traffic in sight. Once the Cessna was over the numbers; the LJ35 was on a half mile final and said that he was executing a missed approach. From all controllers' judgment in the tower; the Cesena traffic would have been through the intersection long before the LJ35 crossed the threshold of Runway 7. Recommendation: after the situation was resolved; the CIC found out that the Approach Control had no idea the Tower had to back taxi. I recommend IDS-4 equipment at the Tower so that the Tower may update it and keep Approach aware of constant changes. If Approach was aware of the closures; maybe they could have given more space between aircraft.

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