37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 423059 |
Time | |
Date | 199812 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : pdk |
State Reference | GA |
Altitude | agl bound lower : 1000 agl bound upper : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | PA-46 Malibu |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Experience | flight time last 90 days : 100 flight time total : 6000 flight time type : 200 |
ASRS Report | 423059 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | Pilot Deviation other |
Narrative:
Approaching pdk from the northwest, I was sequenced #2 for runway 20L to follow a citation. I reported the airport and traffic in sight. Approach control cleared me for a visual to runway 20L, call the tower. I switched to tower frequency and reported #2 for runway 20L. Traffic into pdk was extremely heavy. The tower frequency was jammed with a number of blocked xmissions. In addition to the fixed wing traffic, there were several traffic helicopters coming and going. A helicopter passed beneath me as I was approximately 1 mi out, but was no factor. Tower advised a falcon to depart prior to my arrival and would I be able to accept runway 20R. I advised that I could accept runway 20R but I did not take this as a clearance to land on runway 20R. I thought tower cleared me to land runway 20L and I thought I confirmed cleared runway 20L. The entire time I was on the ILS to runway 20L. At approximately 1/2 mi out, a PA31 pulled into position and hold on runway 20L. I realized this would not work, so I initiated a go around, maintaining runway heading. Crossing the airport boundary, I saw a jet ranger crossing midfield from east to west. We were on an approximately collision course and it did not appear that the helicopter saw me. I turned right, away from the helicopter. As I was turning, the tower operator realized what was happening and asked the helicopter if he had the malibu turning to his right front in sight. I do not recall his reply, if I heard it at all. Also due to communication saturation, I had been unable to advise the tower of my go around. I continued my right turn and made a normal approach to runway 20R. Obviously the tower operator thought I was going to sidestep to runway 20R and I thought I had been cleared to land runway 20L. Although the tower was doing a terrific job sequencing the volume of traffic, saturation prevented adequate communication. In addition to the high volume of fixed wing aircraft, the helicopter traffic flying their own patterns added to the confusion.
Original NASA ASRS Text
Title: PLT OF A CPR PIPER MALIBU PA46 FAILED TO SIDESTEP TO THE OTHER PARALLEL RWY FOR LNDG AFTER ACCEPTING RWY WHEN ASKED BY TWR CTLR. HIS ACTION RESULTED IN CAUSING HIM TO EXECUTE A GAR DUE TO ANOTHER ACFT ON THE RWY FOR TKOF AND SUBSEQUENTLY TAKING EVASIVE ACTION TO AVOID A XTFC HELI. HE THEN CIRCLED DOWNWIND AND LANDED ON THE CORRECT RWY.
Narrative: APCHING PDK FROM THE NW, I WAS SEQUENCED #2 FOR RWY 20L TO FOLLOW A CITATION. I RPTED THE ARPT AND TFC IN SIGHT. APCH CTL CLRED ME FOR A VISUAL TO RWY 20L, CALL THE TWR. I SWITCHED TO TWR FREQ AND RPTED #2 FOR RWY 20L. TFC INTO PDK WAS EXTREMELY HVY. THE TWR FREQ WAS JAMMED WITH A NUMBER OF BLOCKED XMISSIONS. IN ADDITION TO THE FIXED WING TFC, THERE WERE SEVERAL TFC HELIS COMING AND GOING. A HELI PASSED BENEATH ME AS I WAS APPROX 1 MI OUT, BUT WAS NO FACTOR. TWR ADVISED A FALCON TO DEPART PRIOR TO MY ARR AND WOULD I BE ABLE TO ACCEPT RWY 20R. I ADVISED THAT I COULD ACCEPT RWY 20R BUT I DID NOT TAKE THIS AS A CLRNC TO LAND ON RWY 20R. I THOUGHT TWR CLRED ME TO LAND RWY 20L AND I THOUGHT I CONFIRMED CLRED RWY 20L. THE ENTIRE TIME I WAS ON THE ILS TO RWY 20L. AT APPROX 1/2 MI OUT, A PA31 PULLED INTO POS AND HOLD ON RWY 20L. I REALIZED THIS WOULD NOT WORK, SO I INITIATED A GAR, MAINTAINING RWY HDG. XING THE ARPT BOUNDARY, I SAW A JET RANGER XING MIDFIELD FROM E TO W. WE WERE ON AN APPROX COLLISION COURSE AND IT DID NOT APPEAR THAT THE HELI SAW ME. I TURNED R, AWAY FROM THE HELI. AS I WAS TURNING, THE TWR OPERATOR REALIZED WHAT WAS HAPPENING AND ASKED THE HELI IF HE HAD THE MALIBU TURNING TO HIS R FRONT IN SIGHT. I DO NOT RECALL HIS REPLY, IF I HEARD IT AT ALL. ALSO DUE TO COM SATURATION, I HAD BEEN UNABLE TO ADVISE THE TWR OF MY GAR. I CONTINUED MY R TURN AND MADE A NORMAL APCH TO RWY 20R. OBVIOUSLY THE TWR OPERATOR THOUGHT I WAS GOING TO SIDESTEP TO RWY 20R AND I THOUGHT I HAD BEEN CLRED TO LAND RWY 20L. ALTHOUGH THE TWR WAS DOING A TERRIFIC JOB SEQUENCING THE VOLUME OF TFC, SATURATION PREVENTED ADEQUATE COM. IN ADDITION TO THE HIGH VOLUME OF FIXED WING ACFT, THE HELI TFC FLYING THEIR OWN PATTERNS ADDED TO THE CONFUSION.
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.