tvman345 Posted January 26, 2007 Posted January 26, 2007 (edited) This came across my desk today... Thought it would be an interesting read for everyone here: Program: PennSTAR Flight Team3400 Spruce StreetPhila, PA 19104 Type: S-76Operator/Vendor: Other Service Weather: Clear. Not a factor Team: No injuries reported. Patient on board. Description:At approximately 2300 hours, PennCOMM was notified via telephone byanother flight programs dispatch center that one of their aircraft (S-76)was inbound with an interfacility patient to the University ofPennsylvania Medical Center helipad (12th floor, rooftop pad), withan approximate ETA of five (5) minutes. The inbound aircraftscommunication center was immediately informed that the helipad wasoccupied by a PennSTAR aircraft (BK-117) which had just completed a mission,and that the inbound aircraft would need to wait for the PennSTARaircraft to depart before landing. The PennSTAR crew immediatelyproceeded to the aircraft and began preflight procedures. Perimeterhelipad lighting and rotating beacons were operational however floodlighting on the pad was turned-off to preserve night vision for thedeparting aircraft crew. The flight nurse, who was standing fire-watch at the 2 O'clockposition, noticed the inbound aircraft's landing lights approachingover the city and assumed the aircraft would maintain a safe distanceaway. The PennSTAR pilot had completed #1 engine start-up, wasbeginning the engine start cycle on the 2nd engine and had allstrobes and anti-collision lights illuminated. The flight nursenoticed the inbound aircraft approaching, and then crossing the planof the helipad. The flight nurse attempted to signal the incommingaircraft first by waiving arms, then by shining a flashlight into thecockpit of the approaching aircraft. Simultaneously, the PennSTARCommunication Technicians attempted radio contact - without success -with the aircraft on both the PennSTAR and Philadelphia aviation radiofrequencies and by rapidly flashing the perimeter helipad lighting.The inbound aircraft was directly overhead of the PennSTAR aircraftwhen they initiated a go-around departure. Post incident mechanicalinspection revealed no damage to the PennSTAR aircraft. Additional Info:A debriefing of this incident was conducted with theaviation management of both services and several fundamentaloperational mandates were reinforced. The co-pilot of the inboundaircraft indicated that the reflective tape on the flight nurse'shelmet was the first indication of a problem and was what promptedthe go-around. This incident reveals several operationalconsiderations:• The absolute necessity of establishing radio contact with thereceiving facility. No radio contact was made to PennCOMM from thein-bound aircraft.• The necessity of direct aircraft communications.• The importance of visually confirming a clear pad and establishingvisual references, especially at night, prior to landing.• The importance of reflective markings on uniforms/helmets.• The importance of having a crew-member outside the aircraft duringstart-up. The quick, decisive actions of the PennSTAR Flight Nurse andCommunication Technicians were instrumental in averting a disaster. Source: Bob Higgins, Program Director-PennSTAR Flight Team Edited January 26, 2007 by tvman345 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.