37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 567060 |
Time | |
Date | 200211 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : pxr.vortac |
State Reference | AZ |
Altitude | msl bound lower : 7000 msl bound upper : 8000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : p50.tracon |
Operator | general aviation : corporate |
Make Model Name | Citationjet, C525/C526 |
Operating Under FAR Part | Part 91 |
Navigation In Use | other vortac |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : p50.tracon |
Make Model Name | Gulfstream Jet Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 80 flight time total : 6500 flight time type : 640 |
ASRS Report | 567060 |
Person 2 | |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | altitude deviation : overshoot conflict : airborne less severe non adherence : far non adherence : published procedure non adherence : clearance |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued new clearance controller : issued alert |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 7200 vertical : 200 |
Supplementary | |
Problem Areas | Flight Crew Human Performance Environmental Factor |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft is a single pilot without TCASII. I picked up 1 passenger for my return home. This passenger didn't want to situation in the right front seat because he wanted to do some paperwork. Usually, I have a passenger in the right seat to help watch for traffic. My clearance out of ffz was to climb to 4000 ft. The tower said there was traffic passing northeast of the field and to watch for that traffic. After takeoff, I was able to spot airplanes while turning to 300 degrees. When I contacted phx departure, I was cleared to 6000 ft. The sun was low, and with the haze it was difficult to see other airplanes. Departure control was very busy at the time. I engaged the autoplt so I could concentrate on clearing for traffic. I was given a new heading and altitude. I set them in the FMS and continued the departure. Shortly after leveling off at 8000 ft, the controller in a panicked voice, called a traffic conflict. He asked what my altitude was, and I replied 8000 ft. He said my clearance was to 7000 ft, I had traffic at my 3 O'clock position. I immediately looked to the right and never saw the traffic. He then cleared me to 12000 ft. In a couple of mins he came back and gave me a number to call phx when I landed. I called the number and talked to a supervisor. He said that they had listened to the tapes and I had been cleared to 7000 ft and had acknowledged 7000 ft. The conflicting traffic was a gulfstream that was coming in from the northeast. I never did see that traffic. As I concentrated on clearing for VFR traffic, I believe I inadvertently set the wrong altitude in the FMS. By the time the conflict happened, I really didn't remember what altitude I'd been cleared to and assumed it was the altitude I'd set in. The altitude select in the C525 uses a single knob that selects altimeter settings both by angular displacement and the speed the knob is turned. If the knob is turned rapidly, it will change the altitude by thousands or tens of thousands of ft. With the same amount of rotation at a slower rate, it will change the altitude hundreds of ft. I suspect I turned the knob too rapidly and didn't realize it. This has happened before, but I've always caught it before. I have experimented with changing my technique when given headings and altitudes. I've tried to set the numbers in the system and check before responding. I've found this is much too slow for a busy controller. At phx they often give headings, altitudes, altimeter settings in 1 transmission. They expect a quick response or are jumping on you for not listening up. Usually there is no problem with responding and then setting equipment. If there is a lot of radio traffic, it makes it much more difficult to concentrate. I will be more diligent in checking altimeter settings on the FMS in the future.
Original NASA ASRS Text
Title: SINGLE CPR C525 PLT ACKNOWLEDGED ALT ASSIGNMENT CHANGE BUT ENTERS INCORRECT ALT INTO FMS, RESULTING IN AN ALT CONFLICT WITH ANOTHER CPR ACFT.
Narrative: ACFT IS A SINGLE PLT WITHOUT TCASII. I PICKED UP 1 PAX FOR MY RETURN HOME. THIS PAX DIDN'T WANT TO SIT IN THE R FRONT SEAT BECAUSE HE WANTED TO DO SOME PAPERWORK. USUALLY, I HAVE A PAX IN THE R SEAT TO HELP WATCH FOR TFC. MY CLRNC OUT OF FFZ WAS TO CLB TO 4000 FT. THE TWR SAID THERE WAS TFC PASSING NE OF THE FIELD AND TO WATCH FOR THAT TFC. AFTER TKOF, I WAS ABLE TO SPOT AIRPLANES WHILE TURNING TO 300 DEGS. WHEN I CONTACTED PHX DEP, I WAS CLRED TO 6000 FT. THE SUN WAS LOW, AND WITH THE HAZE IT WAS DIFFICULT TO SEE OTHER AIRPLANES. DEP CTL WAS VERY BUSY AT THE TIME. I ENGAGED THE AUTOPLT SO I COULD CONCENTRATE ON CLRING FOR TFC. I WAS GIVEN A NEW HDG AND ALT. I SET THEM IN THE FMS AND CONTINUED THE DEP. SHORTLY AFTER LEVELING OFF AT 8000 FT, THE CTLR IN A PANICKED VOICE, CALLED A TFC CONFLICT. HE ASKED WHAT MY ALT WAS, AND I REPLIED 8000 FT. HE SAID MY CLRNC WAS TO 7000 FT, I HAD TFC AT MY 3 O'CLOCK POS. I IMMEDIATELY LOOKED TO THE R AND NEVER SAW THE TFC. HE THEN CLRED ME TO 12000 FT. IN A COUPLE OF MINS HE CAME BACK AND GAVE ME A NUMBER TO CALL PHX WHEN I LANDED. I CALLED THE NUMBER AND TALKED TO A SUPVR. HE SAID THAT THEY HAD LISTENED TO THE TAPES AND I HAD BEEN CLRED TO 7000 FT AND HAD ACKNOWLEDGED 7000 FT. THE CONFLICTING TFC WAS A GULFSTREAM THAT WAS COMING IN FROM THE NE. I NEVER DID SEE THAT TFC. AS I CONCENTRATED ON CLRING FOR VFR TFC, I BELIEVE I INADVERTENTLY SET THE WRONG ALT IN THE FMS. BY THE TIME THE CONFLICT HAPPENED, I REALLY DIDN'T REMEMBER WHAT ALT I'D BEEN CLRED TO AND ASSUMED IT WAS THE ALT I'D SET IN. THE ALT SELECT IN THE C525 USES A SINGLE KNOB THAT SELECTS ALTIMETER SETTINGS BOTH BY ANGULAR DISPLACEMENT AND THE SPD THE KNOB IS TURNED. IF THE KNOB IS TURNED RAPIDLY, IT WILL CHANGE THE ALT BY THOUSANDS OR TENS OF THOUSANDS OF FT. WITH THE SAME AMOUNT OF ROTATION AT A SLOWER RATE, IT WILL CHANGE THE ALT HUNDREDS OF FT. I SUSPECT I TURNED THE KNOB TOO RAPIDLY AND DIDN'T REALIZE IT. THIS HAS HAPPENED BEFORE, BUT I'VE ALWAYS CAUGHT IT BEFORE. I HAVE EXPERIMENTED WITH CHANGING MY TECHNIQUE WHEN GIVEN HDGS AND ALTS. I'VE TRIED TO SET THE NUMBERS IN THE SYS AND CHK BEFORE RESPONDING. I'VE FOUND THIS IS MUCH TOO SLOW FOR A BUSY CTLR. AT PHX THEY OFTEN GIVE HDGS, ALTS, ALTIMETER SETTINGS IN 1 XMISSION. THEY EXPECT A QUICK RESPONSE OR ARE JUMPING ON YOU FOR NOT LISTENING UP. USUALLY THERE IS NO PROB WITH RESPONDING AND THEN SETTING EQUIP. IF THERE IS A LOT OF RADIO TFC, IT MAKES IT MUCH MORE DIFFICULT TO CONCENTRATE. I WILL BE MORE DILIGENT IN CHKING ALTIMETER SETTINGS ON THE FMS IN THE FUTURE.
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.