37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 467418 |
Time | |
Date | 200003 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : fkr.airport |
State Reference | IN |
Altitude | msl single value : 13500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | artcc : zid.artcc |
Operator | common carrier : air carrier |
Make Model Name | B747 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : vacating altitude |
Route In Use | departure sid : ns enroute airway : v97.airway |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : cfi pilot : atp |
Experience | flight time last 90 days : 20 flight time total : 3250 flight time type : 90 |
ASRS Report | 762 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : far other anomaly other |
Independent Detector | other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued advisory flight crew : took evasive action |
Consequence | other |
Supplementary | |
Problem Areas | ATC Human Performance Airspace Structure Chart Or Publication |
Primary Problem | Airspace Structure |
Situations | |
ATC Facility | procedure or policy : zid.artcc |
Airspace Structure | class e : zid.e |
Narrative:
During one of our routine flts to altitude to release skydivers, we were in close proximity to a B747 and a quick 360 degree turn was required to avoid a possible collision. Since jump run is normally flown directly over the airport into the wind, we fly a rectangular pattern during climb. We were just turning the last leg or jump run leg when I heard the controller informing a connie (number unknown), of a jump aircraft climbing over frankfort. Not knowing his position to us yet, I immediately looked to my right as far behind us as I could see then to my left. At that time I spotted the B747 to my left and slightly high at about 7:30 - 8 O'clock position. I immediately performed a steep r-hand descending turn. At the same time I was receiving a transmission from center of the possible traffic conflict. During our turn I observed the B747 making a shallow left turn. The controllers were very busy that day. During the later portion of our climb pattern we were paralleling or probably diverging from the B747. Both of us were climbing and the B747 speed was considerably faster than ours. When we made the left 90 degree turn, putting us on jump run, this put the B747 at approximately our 8 O'clock position, now convergence. The B747 was climbing to an altitude higher than us and flying directly over the airport. The timing was such that this could have brought us to the same point at the same time. When the controller advised the B747 of their traffic, distance and being a jump plane that triggered me to look behind us, since during the climb I was scanning for aircraft and none were detected. There are several items leading to this situation. We have noticed an increased amount of traffic flying directly over the airport -- a lot of which are on IFR flight plans. The controllers were very busy and we talk to ZAU when most of the traffic flying directly over the frankfort airport originate from ZID. We also have a standing NOTAM on file for skydiving operations, but these are never forwarded to pilots when they get briefings. We attempted to file a NOTAM weekly so this information would be relayed to pilots. However, we were told we can't do that because we have a standing NOTAM. Not that they should avoid the airspace, but it would be helpful if aircraft in the area would know we are there and maybe monitor the unicom frequency. We make advisory calls and monitor unicom as well. That just doesn't seem to be enough. With the increased use of GPS we have more direct flts where indianapolis traffic will fly directly over frankfort. We will now ask the occupants of the aircraft to watch for traffic as they are sitting in the plane climbing to altitude and inform the pilots of any ones detected. The more eyes the better.
Original NASA ASRS Text
Title: A KING AIR B90 CPR SKYDIVE PLT TURNS AND DIVES TO AVOID A CLBING B747 OVERFLYING THE ARPT WHERE HE IS TO DROP SKYDIVERS. FKR, IN.
Narrative: DURING ONE OF OUR ROUTINE FLTS TO ALT TO RELEASE SKYDIVERS, WE WERE IN CLOSE PROX TO A B747 AND A QUICK 360 DEG TURN WAS REQUIRED TO AVOID A POSSIBLE COLLISION. SINCE JUMP RUN IS NORMALLY FLOWN DIRECTLY OVER THE ARPT INTO THE WIND, WE FLY A RECTANGULAR PATTERN DURING CLB. WE WERE JUST TURNING THE LAST LEG OR JUMP RUN LEG WHEN I HEARD THE CTLR INFORMING A CONNIE (NUMBER UNKNOWN), OF A JUMP ACFT CLBING OVER FRANKFORT. NOT KNOWING HIS POS TO US YET, I IMMEDIATELY LOOKED TO MY R AS FAR BEHIND US AS I COULD SEE THEN TO MY L. AT THAT TIME I SPOTTED THE B747 TO MY L AND SLIGHTLY HIGH AT ABOUT 7:30 - 8 O'CLOCK POS. I IMMEDIATELY PERFORMED A STEEP R-HAND DSNDING TURN. AT THE SAME TIME I WAS RECEIVING A XMISSION FROM CTR OF THE POSSIBLE TFC CONFLICT. DURING OUR TURN I OBSERVED THE B747 MAKING A SHALLOW L TURN. THE CTLRS WERE VERY BUSY THAT DAY. DURING THE LATER PORTION OF OUR CLB PATTERN WE WERE PARALLELING OR PROBABLY DIVERGING FROM THE B747. BOTH OF US WERE CLBING AND THE B747 SPD WAS CONSIDERABLY FASTER THAN OURS. WHEN WE MADE THE L 90 DEG TURN, PUTTING US ON JUMP RUN, THIS PUT THE B747 AT APPROX OUR 8 O'CLOCK POS, NOW CONVERGENCE. THE B747 WAS CLBING TO AN ALT HIGHER THAN US AND FLYING DIRECTLY OVER THE ARPT. THE TIMING WAS SUCH THAT THIS COULD HAVE BROUGHT US TO THE SAME POINT AT THE SAME TIME. WHEN THE CTLR ADVISED THE B747 OF THEIR TFC, DISTANCE AND BEING A JUMP PLANE THAT TRIGGERED ME TO LOOK BEHIND US, SINCE DURING THE CLB I WAS SCANNING FOR ACFT AND NONE WERE DETECTED. THERE ARE SEVERAL ITEMS LEADING TO THIS SIT. WE HAVE NOTICED AN INCREASED AMOUNT OF TFC FLYING DIRECTLY OVER THE ARPT -- A LOT OF WHICH ARE ON IFR FLT PLANS. THE CTLRS WERE VERY BUSY AND WE TALK TO ZAU WHEN MOST OF THE TFC FLYING DIRECTLY OVER THE FRANKFORT ARPT ORIGINATE FROM ZID. WE ALSO HAVE A STANDING NOTAM ON FILE FOR SKYDIVING OPS, BUT THESE ARE NEVER FORWARDED TO PLTS WHEN THEY GET BRIEFINGS. WE ATTEMPTED TO FILE A NOTAM WKLY SO THIS INFO WOULD BE RELAYED TO PLTS. HOWEVER, WE WERE TOLD WE CAN'T DO THAT BECAUSE WE HAVE A STANDING NOTAM. NOT THAT THEY SHOULD AVOID THE AIRSPACE, BUT IT WOULD BE HELPFUL IF ACFT IN THE AREA WOULD KNOW WE ARE THERE AND MAYBE MONITOR THE UNICOM FREQ. WE MAKE ADVISORY CALLS AND MONITOR UNICOM AS WELL. THAT JUST DOESN'T SEEM TO BE ENOUGH. WITH THE INCREASED USE OF GPS WE HAVE MORE DIRECT FLTS WHERE INDIANAPOLIS TFC WILL FLY DIRECTLY OVER FRANKFORT. WE WILL NOW ASK THE OCCUPANTS OF THE ACFT TO WATCH FOR TFC AS THEY ARE SITTING IN THE PLANE CLBING TO ALT AND INFORM THE PLTS OF ANY ONES DETECTED. THE MORE EYES THE BETTER.
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.