37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 628120 |
Time | |
Date | 200408 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | special use airspace : zzz.restricted |
State Reference | NJ |
Altitude | agl single value : 800 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | other |
Make Model Name | Helicopter |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | None |
Aircraft 2 | |
Operator | other |
Make Model Name | Military |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 75 flight time total : 8000 flight time type : 4000 |
ASRS Report | 628120 |
Person 2 | |
Affiliation | government : military |
Function | flight crew : single pilot |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : exited penetrated airspace |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While ferrying a county helicopter from cranbury, nj, to philadelphia penn's landing helicopter, I was intercepted by an air force F-14. I made a 180 degree turn and tuned my radio to 121.5, called the fighter aircraft 3 times with no response. Then an air carrier aircraft called and said the fighter wanted me to turn north to exit the 'no fly' area, about 1 mi, which I acknowledged. The F-14 continued to circle my helicopter until I left the area. Due to hectic day's work and maintenance problems with 2 aircraft, I was in a rush to get to philadelphia to get required airworthiness directives accomplished. I had to install spray equipment and continue working until sunset. I failed to call FSS and didn't check NOTAMS or tfr's. Had I called and known about the tfr, I would not have flown to penn's landing. Calling FSS is now a first priority! I was concerned that the F-14 could not communicate with me on 121.5. The air carrier's relay was a life saver!
Original NASA ASRS Text
Title: A UH12E GOV PLT, DURING A FERRY FLT FROM NJ29 TO P72, WAS INTERCEPTED BY AN F-14 WITH WHOM HE WAS UNABLE TO COMMUNICATE UNTIL AN ACR INTERVENED AND PROVIDED THE RPTR WITH INSTRUCTIONS.
Narrative: WHILE FERRYING A COUNTY HELI FROM CRANBURY, NJ, TO PHILADELPHIA PENN'S LNDG HELI, I WAS INTERCEPTED BY AN AIR FORCE F-14. I MADE A 180 DEG TURN AND TUNED MY RADIO TO 121.5, CALLED THE FIGHTER ACFT 3 TIMES WITH NO RESPONSE. THEN AN ACR ACFT CALLED AND SAID THE FIGHTER WANTED ME TO TURN N TO EXIT THE 'NO FLY' AREA, ABOUT 1 MI, WHICH I ACKNOWLEDGED. THE F-14 CONTINUED TO CIRCLE MY HELI UNTIL I LEFT THE AREA. DUE TO HECTIC DAY'S WORK AND MAINT PROBS WITH 2 ACFT, I WAS IN A RUSH TO GET TO PHILADELPHIA TO GET REQUIRED AIRWORTHINESS DIRECTIVES ACCOMPLISHED. I HAD TO INSTALL SPRAY EQUIP AND CONTINUE WORKING UNTIL SUNSET. I FAILED TO CALL FSS AND DIDN'T CHK NOTAMS OR TFR'S. HAD I CALLED AND KNOWN ABOUT THE TFR, I WOULD NOT HAVE FLOWN TO PENN'S LNDG. CALLING FSS IS NOW A FIRST PRIORITY! I WAS CONCERNED THAT THE F-14 COULD NOT COMMUNICATE WITH ME ON 121.5. THE ACR'S RELAY WAS A LIFE SAVER!
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.