37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 289328 |
Time | |
Date | 199411 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tus |
State Reference | AZ |
Altitude | msl bound lower : 55005 msl bound upper : 5500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : tus |
Operator | general aviation : personal |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude cruise other |
Route In Use | enroute : direct |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Helicopter |
Operating Under FAR Part | other : unknown |
Flight Phase | cruise other cruise other |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 16 flight time total : 1325 flight time type : 554 |
ASRS Report | 289328 |
Person 2 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
Events | |
Anomaly | conflict : nmac |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action other |
Consequence | Other |
Miss Distance | horizontal : 200 vertical : 100 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This near-miss incident occurred during departure phase of flight from tucson international airport (tus) to payson, az, municipal airport (E69) and involved my aircraft and a helicopter that was apparently inbound to tus. Prior to our takeoff, tucson clearance delivery was advised that our planned departure heading was 340 direct payson, with climb to cruise altitude of 3800 ft MSL. Our takeoff clearance from tus included a left downwind departure from runway 11L, but was amended shortly after we were airborne by tower request that we proceed directly to 'a' mountain (a VFR landmark approximately 9 NM northwest of tus VOR on radial 325), and resume our own navigation thereafter. Just prior to crossing 'a' mountain we were handed off to tucson departure control and reported thereto climbing through 5500 ft MSL. Departure control issued us an altitude restr to remain at or below 5500 ft MSL and expect further climb clearance in about 4 min. Nothing was said about route of flight, so we continued to 'a' mountain as tower had requested, turned nward from there, and came level at 5500 ft MSL. About 3 NM north of 'a' mountain, while level at 5500 ft MSL, we observed a helicopter coming opposite direction and performing an abrupt descending right turn, apparently as a deviation maneuver to avoid our flight path. We estimate that the helicopter came within 200 ft horizontal and was approximately 100 ft below and to our left when we passed. We seem to recall hearing tucson approach advise the helicopter pilot of our position and altitude, but do not recall being advised conversely that a helicopter was a factor in our traffic situation. As to probable cause of this incident, it seems uncertain whether ATC didn't provide adequate routing/altitude instructions to avoid conflict or the helicopter pilot didn't understand the significance of ATC's traffic report. We attempted to maintain vigilance for other traffic (as always), but simply didn't see the helicopter until it was already in the descending turn. (1 possible factor may be that the helicopter pilot didn't expect our closure rate to be as fast as it was. Our airspeed at the time was 120 KTS and increasing, but we were reported as a 'grumman at 5500 ft...' and many pilots of higher-performing aircraft expect or perceive small planes to be relatively slow.)
Original NASA ASRS Text
Title: SMA HAS NMAC WITH HELI ON DEP TO ASSIGNED ALT.
Narrative: THIS NEAR-MISS INCIDENT OCCURRED DURING DEP PHASE OF FLT FROM TUCSON INTL ARPT (TUS) TO PAYSON, AZ, MUNICIPAL ARPT (E69) AND INVOLVED MY ACFT AND A HELI THAT WAS APPARENTLY INBOUND TO TUS. PRIOR TO OUR TKOF, TUCSON CLRNC DELIVERY WAS ADVISED THAT OUR PLANNED DEP HDG WAS 340 DIRECT PAYSON, WITH CLB TO CRUISE ALT OF 3800 FT MSL. OUR TKOF CLRNC FROM TUS INCLUDED A L DOWNWIND DEP FROM RWY 11L, BUT WAS AMENDED SHORTLY AFTER WE WERE AIRBORNE BY TWR REQUEST THAT WE PROCEED DIRECTLY TO 'A' MOUNTAIN (A VFR LANDMARK APPROX 9 NM NW OF TUS VOR ON RADIAL 325), AND RESUME OUR OWN NAV THEREAFTER. JUST PRIOR TO XING 'A' MOUNTAIN WE WERE HANDED OFF TO TUCSON DEP CTL AND RPTED THERETO CLBING THROUGH 5500 FT MSL. DEP CTL ISSUED US AN ALT RESTR TO REMAIN AT OR BELOW 5500 FT MSL AND EXPECT FURTHER CLB CLRNC IN ABOUT 4 MIN. NOTHING WAS SAID ABOUT RTE OF FLT, SO WE CONTINUED TO 'A' MOUNTAIN AS TWR HAD REQUESTED, TURNED NWARD FROM THERE, AND CAME LEVEL AT 5500 FT MSL. ABOUT 3 NM N OF 'A' MOUNTAIN, WHILE LEVEL AT 5500 FT MSL, WE OBSERVED A HELI COMING OPPOSITE DIRECTION AND PERFORMING AN ABRUPT DSNDING R TURN, APPARENTLY AS A DEV MANEUVER TO AVOID OUR FLT PATH. WE ESTIMATE THAT THE HELI CAME WITHIN 200 FT HORIZ AND WAS APPROX 100 FT BELOW AND TO OUR L WHEN WE PASSED. WE SEEM TO RECALL HEARING TUCSON APCH ADVISE THE HELI PLT OF OUR POS AND ALT, BUT DO NOT RECALL BEING ADVISED CONVERSELY THAT A HELI WAS A FACTOR IN OUR TFC SIT. AS TO PROBABLE CAUSE OF THIS INCIDENT, IT SEEMS UNCERTAIN WHETHER ATC DIDN'T PROVIDE ADEQUATE RTING/ALT INSTRUCTIONS TO AVOID CONFLICT OR THE HELI PLT DIDN'T UNDERSTAND THE SIGNIFICANCE OF ATC'S TFC RPT. WE ATTEMPTED TO MAINTAIN VIGILANCE FOR OTHER TFC (AS ALWAYS), BUT SIMPLY DIDN'T SEE THE HELI UNTIL IT WAS ALREADY IN THE DSNDING TURN. (1 POSSIBLE FACTOR MAY BE THAT THE HELI PLT DIDN'T EXPECT OUR CLOSURE RATE TO BE AS FAST AS IT WAS. OUR AIRSPD AT THE TIME WAS 120 KTS AND INCREASING, BUT WE WERE RPTED AS A 'GRUMMAN AT 5500 FT...' AND MANY PLTS OF HIGHER-PERFORMING ACFT EXPECT OR PERCEIVE SMALL PLANES TO BE RELATIVELY SLOW.)
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.