Narrative:

Near end of pleasure flight in local area; flew at 2300 ft MSL through busy area -- eastbound departure from ads at 2000 ft MSL; and arrs at 2500 ft MSL; and floor of class B at 3000 ft MSL. I flew from right seat; allowing friend in left seat to manipulate controls in cruise northbound. I was watching display (which depicts traffic); visual scan outside; and casually chatting with passenger. Monitored 121.5 but not on regional approach yet. Traffic alert activated. Display showed 'pop-up' traffic 1/4 mi at 10 O'clock position; 200 ft low. Visual scan could not see target. Display showed target slide to 9 O'clock position. I turned 20 degrees to right and climbed. Traffic alert activated again -- still no visual contact as passenger and I both scanned furiously. Now depiction showed traffic at altitude though I had climbed 300 ft and it showed traffic merged with my position. Suddenly saw traffic at 11 O'clock position and approximately 40 ft high; 200 ft horizontal distance with no movement on windscreen -- perfect collision course. (Altitude now approximately 2500 ft; then aircraft appeared level and though slightly low when first saw him; I was still in climb.) I immediately banked left 90 degrees to turn and pass behind the aircraft. It was a single engine aircraft. Other aircraft did not maneuver and continued flying level at 2500 ft MSL eastbound. I presume he/she never saw me. I estimate passing within 100 ft horizontal and 20 ft low distance from other aircraft. Had I not been banking so I should have been able to read tail number and see faces. My assessment: other aircraft apparently took off; departed area at 2000 ft MSL per standard VFR procedures at ads. At the time I got traffic alert; I climbed but apparently he did; too. We both ended up at 2500 ft MSL. In retrospect; the ads procedures state for departures to maintain 2000 ft MSL until clear of class D. Most people stay at 2000 ft till approximately 10 mi away from airport. That was about the point he began to climb (at 2000 ft). Also; after incident; I checked settings on avidyne system. I forget which setting the traffic alert was on -- I think 'above;' but it was not on 'normal' or on 'unlimited' which would have given more advanced warning. At 'above' it would only give depictions and alerts at traffic near/at my altitude or above. Neither one of us did anything wrong; but conflict still arose in a busy area underneath class B where VFR depart; arrive; and transition in different directions. After landing; I went to the flight school and spoke with chief pilot to inform them of near midair collision they might not have been aware of. My scan and attention outside was adequate though not productive; and though traffic alert saved us; a better setting on it could have helped us avoid it in the first place. Could've gone to regional approach for TA's though wasn't quite ready to return to ads yet. Suggestion: maybe departure procedures from ads should ask planes to stay at 2000 ft MSL for 20 NM (which is edge of class B to north and east) since arrs will be at 2500 ft MSL between 15-20 mi out.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN SR22 BENEATH DFW CLASS B HAD A NMAC WITH ANOTHER ACFT AT 2500 FT MSL.

Narrative: NEAR END OF PLEASURE FLT IN LCL AREA; FLEW AT 2300 FT MSL THROUGH BUSY AREA -- EBOUND DEP FROM ADS AT 2000 FT MSL; AND ARRS AT 2500 FT MSL; AND FLOOR OF CLASS B AT 3000 FT MSL. I FLEW FROM R SEAT; ALLOWING FRIEND IN L SEAT TO MANIPULATE CTLS IN CRUISE NBOUND. I WAS WATCHING DISPLAY (WHICH DEPICTS TFC); VISUAL SCAN OUTSIDE; AND CASUALLY CHATTING WITH PAX. MONITORED 121.5 BUT NOT ON REGIONAL APCH YET. TFC ALERT ACTIVATED. DISPLAY SHOWED 'POP-UP' TFC 1/4 MI AT 10 O'CLOCK POS; 200 FT LOW. VISUAL SCAN COULD NOT SEE TARGET. DISPLAY SHOWED TARGET SLIDE TO 9 O'CLOCK POS. I TURNED 20 DEGS TO R AND CLBED. TFC ALERT ACTIVATED AGAIN -- STILL NO VISUAL CONTACT AS PAX AND I BOTH SCANNED FURIOUSLY. NOW DEPICTION SHOWED TFC AT ALT THOUGH I HAD CLBED 300 FT AND IT SHOWED TFC MERGED WITH MY POS. SUDDENLY SAW TFC AT 11 O'CLOCK POS AND APPROX 40 FT HIGH; 200 FT HORIZ DISTANCE WITH NO MOVEMENT ON WINDSCREEN -- PERFECT COLLISION COURSE. (ALT NOW APPROX 2500 FT; THEN ACFT APPEARED LEVEL AND THOUGH SLIGHTLY LOW WHEN FIRST SAW HIM; I WAS STILL IN CLB.) I IMMEDIATELY BANKED L 90 DEGS TO TURN AND PASS BEHIND THE ACFT. IT WAS A SINGLE ENG ACFT. OTHER ACFT DID NOT MANEUVER AND CONTINUED FLYING LEVEL AT 2500 FT MSL EBOUND. I PRESUME HE/SHE NEVER SAW ME. I ESTIMATE PASSING WITHIN 100 FT HORIZ AND 20 FT LOW DISTANCE FROM OTHER ACFT. HAD I NOT BEEN BANKING SO I SHOULD HAVE BEEN ABLE TO READ TAIL NUMBER AND SEE FACES. MY ASSESSMENT: OTHER ACFT APPARENTLY TOOK OFF; DEPARTED AREA AT 2000 FT MSL PER STANDARD VFR PROCS AT ADS. AT THE TIME I GOT TFC ALERT; I CLBED BUT APPARENTLY HE DID; TOO. WE BOTH ENDED UP AT 2500 FT MSL. IN RETROSPECT; THE ADS PROCS STATE FOR DEPS TO MAINTAIN 2000 FT MSL UNTIL CLEAR OF CLASS D. MOST PEOPLE STAY AT 2000 FT TILL APPROX 10 MI AWAY FROM AIRPORT. THAT WAS ABOUT THE POINT HE BEGAN TO CLB (AT 2000 FT). ALSO; AFTER INCIDENT; I CHKED SETTINGS ON AVIDYNE SYS. I FORGET WHICH SETTING THE TFC ALERT WAS ON -- I THINK 'ABOVE;' BUT IT WAS NOT ON 'NORMAL' OR ON 'UNLIMITED' WHICH WOULD HAVE GIVEN MORE ADVANCED WARNING. AT 'ABOVE' IT WOULD ONLY GIVE DEPICTIONS AND ALERTS AT TFC NEAR/AT MY ALT OR ABOVE. NEITHER ONE OF US DID ANYTHING WRONG; BUT CONFLICT STILL AROSE IN A BUSY AREA UNDERNEATH CLASS B WHERE VFR DEPART; ARRIVE; AND TRANSITION IN DIFFERENT DIRECTIONS. AFTER LNDG; I WENT TO THE FLT SCHOOL AND SPOKE WITH CHIEF PLT TO INFORM THEM OF NMAC THEY MIGHT NOT HAVE BEEN AWARE OF. MY SCAN AND ATTN OUTSIDE WAS ADEQUATE THOUGH NOT PRODUCTIVE; AND THOUGH TFC ALERT SAVED US; A BETTER SETTING ON IT COULD HAVE HELPED US AVOID IT IN THE FIRST PLACE. COULD'VE GONE TO REGIONAL APCH FOR TA'S THOUGH WASN'T QUITE READY TO RETURN TO ADS YET. SUGGESTION: MAYBE DEP PROCS FROM ADS SHOULD ASK PLANES TO STAY AT 2000 FT MSL FOR 20 NM (WHICH IS EDGE OF CLASS B TO N AND E) SINCE ARRS WILL BE AT 2500 FT MSL BTWN 15-20 MI OUT.

Data retrieved from NASA's ASRS site as of January 2009 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.