 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
PA32-300 on IFR flight plan noticed twin engine aircraft reverse course and pass within 6000 ft. Approach control made no call of traffic. When communication made with controller, he claimed he had been trying to make contact reference the traffic. Had checked NOTAMS earlier and no mention of jumping in this area.
| Attributes | |
| ACN | 347290 |
| Time | |
| Date | 199609 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : etx |
| State Reference | PA |
| Altitude | msl bound lower : 4000 msl bound upper : 4000 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : phl |
| Operator | general aviation : personal |
| Make Model Name | PA-32 Cherokee Six/Lance/Saratoga |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Route In Use | enroute : direct |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private pilot : instrument |
| Experience | flight time last 90 days : 42 flight time total : 320 flight time type : 221 |
| ASRS Report | 347290 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : commercial |
| Events | |
| Anomaly | conflict : airborne less severe |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action |
| Consequence | Other |
| Miss Distance | horizontal : 6000 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I was on IFR flight plan, direct ptw at 4000 ft after check-in on 123.8. Noticed twin engine aircraft make 180 degree turn to my right back to west. I wondered why ATC did not call out potential conflict. Checked radios all seemed to be operating correctly -- no evidence of stuck microphone. I called to ATC who claimed to have been trying to reach me about jumpers in my path! Before takeoff, I checked with williamsport FSS and WX and NOTAMS. I specifically requested jumping activity south of abe, near ptw -- none notamed. Questioned whether my radio was inoperative. Questioned whether ATC was calling out on my assigned frequency. Questioned why no NOTAM on jumping -- my call to FSS was within 45 mins of passing jump point.
Original NASA ASRS Text
Title: PA32-300 ON IFR FLT PLAN NOTICED TWIN ENG ACFT REVERSE COURSE AND PASS WITHIN 6000 FT. APCH CTL MADE NO CALL OF TFC. WHEN COM MADE WITH CTLR, HE CLAIMED HE HAD BEEN TRYING TO MAKE CONTACT REF THE TFC. HAD CHKED NOTAMS EARLIER AND NO MENTION OF JUMPING IN THIS AREA.
Narrative: I WAS ON IFR FLT PLAN, DIRECT PTW AT 4000 FT AFTER CHK-IN ON 123.8. NOTICED TWIN ENG ACFT MAKE 180 DEG TURN TO MY R BACK TO W. I WONDERED WHY ATC DID NOT CALL OUT POTENTIAL CONFLICT. CHKED RADIOS ALL SEEMED TO BE OPERATING CORRECTLY -- NO EVIDENCE OF STUCK MIKE. I CALLED TO ATC WHO CLAIMED TO HAVE BEEN TRYING TO REACH ME ABOUT JUMPERS IN MY PATH! BEFORE TKOF, I CHKED WITH WILLIAMSPORT FSS AND WX AND NOTAMS. I SPECIFICALLY REQUESTED JUMPING ACTIVITY S OF ABE, NEAR PTW -- NONE NOTAMED. QUESTIONED WHETHER MY RADIO WAS INOP. QUESTIONED WHETHER ATC WAS CALLING OUT ON MY ASSIGNED FREQ. QUESTIONED WHY NO NOTAM ON JUMPING -- MY CALL TO FSS WAS WITHIN 45 MINS OF PASSING JUMP POINT.
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.