 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of an small aircraft sel made go around when observing a helicopter holding on approach end of the runway to which he was on final approach for landing at an uncontrolled airport.
| Attributes | |
| ACN | 397891 |
| Time | |
| Date | 199803 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : pym |
| State Reference | MA |
| Altitude | msl bound lower : 600 msl bound upper : 600 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Operator | general aviation : personal |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach landing : go around other |
| Route In Use | approach : visual |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | Helicopter |
| Operating Under FAR Part | other : unknown |
| Flight Phase | climbout : takeoff ground : holding |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : private |
| Experience | flight time last 90 days : 18 flight time total : 2875 flight time type : 2100 |
| ASRS Report | 397891 |
| Person 2 | |
| Function | flight crew : single pilot |
| Events | |
| Anomaly | conflict : nmac other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action |
| Consequence | Other |
| Miss Distance | horizontal : 300 vertical : 500 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
Narrative:
I was on short final approach to runway 24 and a helicopter sitting on the approach end of runway 24 announced he was 'making a running departure' from the runway. This was the only transmission I had heard and I did not see him until at approximately 600 ft MSL. I turned to the right announcing on 123.0 that I was taking evasive action and climbed to pattern altitude (150 ft MSL) then turned left crosswind and re-entered downwind and continued on to land. Shortly thereafter I brought the aircraft to FBO who had just completed the annual inspection because the newly installed alternator was inoperative. I was operating on battery alone. I suspect, and since FBO saw running lights and landing lights and heard my downwind, base and final announcements there was probably no relation to cause of conflict. It was not what I'd consider a close/near miss -- only that I had to make a go around. I know of no violations on my part. I wonder if helicopters should make 'running departures' from active runways?
Original NASA ASRS Text
Title: PLT OF AN SMA SEL MADE GAR WHEN OBSERVING A HELI HOLDING ON APCH END OF THE RWY TO WHICH HE WAS ON FINAL APCH FOR LNDG AT AN UNCTLED ARPT.
Narrative: I WAS ON SHORT FINAL APCH TO RWY 24 AND A HELI SITTING ON THE APCH END OF RWY 24 ANNOUNCED HE WAS 'MAKING A RUNNING DEP' FROM THE RWY. THIS WAS THE ONLY XMISSION I HAD HEARD AND I DID NOT SEE HIM UNTIL AT APPROX 600 FT MSL. I TURNED TO THE R ANNOUNCING ON 123.0 THAT I WAS TAKING EVASIVE ACTION AND CLBED TO PATTERN ALT (150 FT MSL) THEN TURNED L XWIND AND RE-ENTERED DOWNWIND AND CONTINUED ON TO LAND. SHORTLY THEREAFTER I BROUGHT THE ACFT TO FBO WHO HAD JUST COMPLETED THE ANNUAL INSPECTION BECAUSE THE NEWLY INSTALLED ALTERNATOR WAS INOP. I WAS OPERATING ON BATTERY ALONE. I SUSPECT, AND SINCE FBO SAW RUNNING LIGHTS AND LNDG LIGHTS AND HEARD MY DOWNWIND, BASE AND FINAL ANNOUNCEMENTS THERE WAS PROBABLY NO RELATION TO CAUSE OF CONFLICT. IT WAS NOT WHAT I'D CONSIDER A CLOSE/NEAR MISS -- ONLY THAT I HAD TO MAKE A GAR. I KNOW OF NO VIOLATIONS ON MY PART. I WONDER IF HELIS SHOULD MAKE 'RUNNING DEPS' FROM ACTIVE RWYS?
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.