Narrative:

On departure from dfw runway 31L we turned as assigned to 240 degrees and climbed to 2000 ft MSL. Tower handed us off to regional departure. Regional departure was unable to identify our aircraft. We made squawk code changes as requested and continued to fly the 240 degree assigned heading. The 240 degree heading caused our aircraft to penetrate ftw class D airspace. TA was issued with no RA. Traffic was using north runways at ftw. We elected to maintain assigned heading of 240 degrees, as to not create conflict on approach path to runway 34R at ftw. Upon aircraft identify from regional departure, we were given a climb, turn to 290 degrees, and continued the kingdom 5 departure (KING5.TTT). Quicker climb or greater turn on departure from runway 31L could very well remedy the problem.

Google
 

Original NASA ASRS Text

Title: TRACON UNABLE TO MAKE RADAR CONTACT WITH DEPARTING ACFT.

Narrative: ON DEP FROM DFW RWY 31L WE TURNED AS ASSIGNED TO 240 DEGS AND CLBED TO 2000 FT MSL. TWR HANDED US OFF TO REGIONAL DEP. REGIONAL DEP WAS UNABLE TO IDENT OUR ACFT. WE MADE SQUAWK CODE CHANGES AS REQUESTED AND CONTINUED TO FLY THE 240 DEG ASSIGNED HEADING. THE 240 DEG HDG CAUSED OUR ACFT TO PENETRATE FTW CLASS D AIRSPACE. TA WAS ISSUED WITH NO RA. TFC WAS USING N RWYS AT FTW. WE ELECTED TO MAINTAIN ASSIGNED HEADING OF 240 DEGS, AS TO NOT CREATE CONFLICT ON APCH PATH TO RWY 34R AT FTW. UPON ACFT IDENT FROM REGIONAL DEP, WE WERE GIVEN A CLB, TURN TO 290 DEGS, AND CONTINUED THE KINGDOM 5 DEP (KING5.TTT). QUICKER CLB OR GREATER TURN ON DEP FROM RWY 31L COULD VERY WELL REMEDY THE PROB.

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.