37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 468215 |
Time | |
Date | 200004 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dfw.airport |
State Reference | TX |
Altitude | msl bound lower : 9000 msl bound upper : 10500 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : d10.tracon |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : enroute altitude change |
Route In Use | enroute : on vectors |
Flight Plan | VFR |
Aircraft 2 | |
Controlling Facilities | tracon : d10.tracon |
Operator | common carrier : air carrier |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure : on vectors departure sid : joe pool |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : private |
Experience | flight time last 90 days : 90 flight time total : 240 flight time type : 82 |
ASRS Report | 468215 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 18000 flight time type : 1000 |
ASRS Report | 468627 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude conflict : airborne critical inflight encounter other non adherence : clearance non adherence : far non adherence : published procedure non adherence : required legal separation other spatial deviation |
Independent Detector | atc equipment : conflict alert aircraft equipment : tcas other controllera other controllerb |
Resolutory Action | controller : issued new clearance flight crew : took evasive action |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Miss Distance | horizontal : 1000 vertical : 100 |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance Weather Airspace Structure |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation Operational Error |
Narrative:
I was flying a C172 skyhawk VFR from brooks county, tx, to tulsa, ok, and the route of flight was through dallas class B airspace. I departed brooks county and landed at austin, tx, for fuel, then I departed austin and climbed out through a clearing of broken clouds. When we came close to dallas the ceiling began gradually rising and I asked to climb from 9500 ft to 11500 ft to keep clear of clouds. The controller cleared me to 11500 ft. I started my climb, but the plane's performance did not allow for such high altitude due to lack of power and leveled off at 11000 ft. The controller asked me to climb as fast as I could to 11500 ft. I replied that I was unable to reach that altitude and cleared me to descend. The controller had given me a heading of 350 degrees and I asked if I could turn to heading 330 degrees, but he declined that due to traffic. At this time I was about 1/2 mi from the clouds. (If I would have gotten the heading I asked for, I would have been clear of the clouds.) as I kept my heading of 350 degrees, I entered the clouds at 10500 ft and was IMC. I got a call from the controller and at that time I told him I was IMC and I asked for a descent to VFR conditions. The controller asked me if I wanted to file an IFR flight plan, and I replied 'yes.' then he asked me if I was properly rated for IFR flight. My answer was 'negative.' my initial answer of 'yes' was due to a misunderstanding and stress to get myself out of these IMC conditions. Then he cleared me to descend to VFR conditions and I immediately started my descent and was descending about 1000 FPM. As I was descending, the controller asked me to turn to the right on a new heading because of traffic ahead. The controller talked so fast that I did not get the heading he had given me, so I turned immediately 30 degrees to the right and asked the controller to repeat the heading, but I never got the heading from him. As we broke out of the clouds at 9000 ft, we saw an MD80 to our left about 1 mi and 100 ft below in a 45 degree turn to the right. After that, I asked to descend further down to be able to remain VFR. After we were through the airspace, I was asked to change to another controller and he asked me to call him as soon as I landed in tulsa. At that point we did not know how serious the situation was. As I landed in tulsa, I called dallas ATC and was informed that we almost had a midair collision with an MD80 and that the TCASII of that airplane had warned the pilot of possible collision and the captain of that airplane had entered a 45 degree turn to the right to avoid a collision. The controller that I spoke to informed me that the controller covering my area of flight was a fairly new employee and that he did not know how to handle the situation, but that he was familiar with his area. This controller also told me that they were trying to free him of his area so he could move over to the area I was flying in so he could take the right action, but he was too busy to be able to move from his screen, and he also told me that the controller did not want to frighten me by telling me about the MD80. I understand that my mistake was to enter the clouds instead of making a 180 degree turn before entering the clouds and avoid IMC at all cost, as I am not an instrument rated pilot. However, I have gotten about 25 instrument lessons as I am working on my instrument rating and the reason I did not make that turn was because I did not want to make any deviations on my heading because the controller had assigned me the heading of 350 degrees and declined any deviation due to other traffic. It is clear that the near collision was due to the controller clearing me to descend into VFR conditions on a collision course with the MD80. Also, after I departed the class B airspace, 2 of my passenger informed me they heard him give me a 10 degree heading change to the right, it is almost certain that if I had not made a 30 degree turn to the right the path of the 2 planes would have been a lot closer. I am a foreign pilot and I have noticed that some controllers are almost unreadable and in this case he got so tense when he saw that the planes were on a colliding course he started talking fast and unclr. I also want to inform you that the controller never asked me if I wanted to declare an emergency, which the situation was not until he cleared me to descend in front of the MD80. He should have waited for me to pass the MD80 and have me descend after we passed the MD80. My question is, why is an ATC controller not fully capable of handling sits like this controling in class B airspace? I am fully aware of my mistake of entering the clouds and that is an experience that I will put to good use in my flying career as a private pilot, as this incident occurred I am 1/2 way through my instrument training with around 25 instrument hours and will finish the written within the next 2 months.
Original NASA ASRS Text
Title: A PVT PLT FLIES INTO THE CLASS B AIRSPACE OF DFW, NEARLY HITTING AN MD80 WHO HAD TURNED INTO THE C172 WHILE DSNDING ON A TCASII RA 5 MI E OF DFW, TX.
Narrative: I WAS FLYING A C172 SKYHAWK VFR FROM BROOKS COUNTY, TX, TO TULSA, OK, AND THE RTE OF FLT WAS THROUGH DALLAS CLASS B AIRSPACE. I DEPARTED BROOKS COUNTY AND LANDED AT AUSTIN, TX, FOR FUEL, THEN I DEPARTED AUSTIN AND CLBED OUT THROUGH A CLRING OF BROKEN CLOUDS. WHEN WE CAME CLOSE TO DALLAS THE CEILING BEGAN GRADUALLY RISING AND I ASKED TO CLB FROM 9500 FT TO 11500 FT TO KEEP CLR OF CLOUDS. THE CTLR CLRED ME TO 11500 FT. I STARTED MY CLB, BUT THE PLANE'S PERFORMANCE DID NOT ALLOW FOR SUCH HIGH ALT DUE TO LACK OF PWR AND LEVELED OFF AT 11000 FT. THE CTLR ASKED ME TO CLB AS FAST AS I COULD TO 11500 FT. I REPLIED THAT I WAS UNABLE TO REACH THAT ALT AND CLRED ME TO DSND. THE CTLR HAD GIVEN ME A HDG OF 350 DEGS AND I ASKED IF I COULD TURN TO HDG 330 DEGS, BUT HE DECLINED THAT DUE TO TFC. AT THIS TIME I WAS ABOUT 1/2 MI FROM THE CLOUDS. (IF I WOULD HAVE GOTTEN THE HDG I ASKED FOR, I WOULD HAVE BEEN CLR OF THE CLOUDS.) AS I KEPT MY HDG OF 350 DEGS, I ENTERED THE CLOUDS AT 10500 FT AND WAS IMC. I GOT A CALL FROM THE CTLR AND AT THAT TIME I TOLD HIM I WAS IMC AND I ASKED FOR A DSCNT TO VFR CONDITIONS. THE CTLR ASKED ME IF I WANTED TO FILE AN IFR FLT PLAN, AND I REPLIED 'YES.' THEN HE ASKED ME IF I WAS PROPERLY RATED FOR IFR FLT. MY ANSWER WAS 'NEGATIVE.' MY INITIAL ANSWER OF 'YES' WAS DUE TO A MISUNDERSTANDING AND STRESS TO GET MYSELF OUT OF THESE IMC CONDITIONS. THEN HE CLRED ME TO DSND TO VFR CONDITIONS AND I IMMEDIATELY STARTED MY DSCNT AND WAS DSNDING ABOUT 1000 FPM. AS I WAS DSNDING, THE CTLR ASKED ME TO TURN TO THE R ON A NEW HDG BECAUSE OF TFC AHEAD. THE CTLR TALKED SO FAST THAT I DID NOT GET THE HDG HE HAD GIVEN ME, SO I TURNED IMMEDIATELY 30 DEGS TO THE R AND ASKED THE CTLR TO REPEAT THE HDG, BUT I NEVER GOT THE HDG FROM HIM. AS WE BROKE OUT OF THE CLOUDS AT 9000 FT, WE SAW AN MD80 TO OUR L ABOUT 1 MI AND 100 FT BELOW IN A 45 DEG TURN TO THE R. AFTER THAT, I ASKED TO DSND FURTHER DOWN TO BE ABLE TO REMAIN VFR. AFTER WE WERE THROUGH THE AIRSPACE, I WAS ASKED TO CHANGE TO ANOTHER CTLR AND HE ASKED ME TO CALL HIM AS SOON AS I LANDED IN TULSA. AT THAT POINT WE DID NOT KNOW HOW SERIOUS THE SIT WAS. AS I LANDED IN TULSA, I CALLED DALLAS ATC AND WAS INFORMED THAT WE ALMOST HAD A MIDAIR COLLISION WITH AN MD80 AND THAT THE TCASII OF THAT AIRPLANE HAD WARNED THE PLT OF POSSIBLE COLLISION AND THE CAPT OF THAT AIRPLANE HAD ENTERED A 45 DEG TURN TO THE R TO AVOID A COLLISION. THE CTLR THAT I SPOKE TO INFORMED ME THAT THE CTLR COVERING MY AREA OF FLT WAS A FAIRLY NEW EMPLOYEE AND THAT HE DID NOT KNOW HOW TO HANDLE THE SIT, BUT THAT HE WAS FAMILIAR WITH HIS AREA. THIS CTLR ALSO TOLD ME THAT THEY WERE TRYING TO FREE HIM OF HIS AREA SO HE COULD MOVE OVER TO THE AREA I WAS FLYING IN SO HE COULD TAKE THE RIGHT ACTION, BUT HE WAS TOO BUSY TO BE ABLE TO MOVE FROM HIS SCREEN, AND HE ALSO TOLD ME THAT THE CTLR DID NOT WANT TO FRIGHTEN ME BY TELLING ME ABOUT THE MD80. I UNDERSTAND THAT MY MISTAKE WAS TO ENTER THE CLOUDS INSTEAD OF MAKING A 180 DEG TURN BEFORE ENTERING THE CLOUDS AND AVOID IMC AT ALL COST, AS I AM NOT AN INST RATED PLT. HOWEVER, I HAVE GOTTEN ABOUT 25 INST LESSONS AS I AM WORKING ON MY INST RATING AND THE REASON I DID NOT MAKE THAT TURN WAS BECAUSE I DID NOT WANT TO MAKE ANY DEVS ON MY HDG BECAUSE THE CTLR HAD ASSIGNED ME THE HDG OF 350 DEGS AND DECLINED ANY DEV DUE TO OTHER TFC. IT IS CLR THAT THE NEAR COLLISION WAS DUE TO THE CTLR CLRING ME TO DSND INTO VFR CONDITIONS ON A COLLISION COURSE WITH THE MD80. ALSO, AFTER I DEPARTED THE CLASS B AIRSPACE, 2 OF MY PAX INFORMED ME THEY HEARD HIM GIVE ME A 10 DEG HDG CHANGE TO THE R, IT IS ALMOST CERTAIN THAT IF I HAD NOT MADE A 30 DEG TURN TO THE R THE PATH OF THE 2 PLANES WOULD HAVE BEEN A LOT CLOSER. I AM A FOREIGN PLT AND I HAVE NOTICED THAT SOME CTLRS ARE ALMOST UNREADABLE AND IN THIS CASE HE GOT SO TENSE WHEN HE SAW THAT THE PLANES WERE ON A COLLIDING COURSE HE STARTED TALKING FAST AND UNCLR. I ALSO WANT TO INFORM YOU THAT THE CTLR NEVER ASKED ME IF I WANTED TO DECLARE AN EMER, WHICH THE SIT WAS NOT UNTIL HE CLRED ME TO DSND IN FRONT OF THE MD80. HE SHOULD HAVE WAITED FOR ME TO PASS THE MD80 AND HAVE ME DSND AFTER WE PASSED THE MD80. MY QUESTION IS, WHY IS AN ATC CTLR NOT FULLY CAPABLE OF HANDLING SITS LIKE THIS CTLING IN CLASS B AIRSPACE? I AM FULLY AWARE OF MY MISTAKE OF ENTERING THE CLOUDS AND THAT IS AN EXPERIENCE THAT I WILL PUT TO GOOD USE IN MY FLYING CAREER AS A PVT PLT, AS THIS INCIDENT OCCURRED I AM 1/2 WAY THROUGH MY INST TRAINING WITH AROUND 25 INST HRS AND WILL FINISH THE WRITTEN WITHIN THE NEXT 2 MONTHS.
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.