Narrative:

On approach to runway 22L at ewr. Passing approximately 1800' MSL on G/south I spotted flashing lights ahead, slightly left of the nose and slightly lower than our aircraft. As it moved across our flight path, I could then see and realized it was another aircraft. As it moved to the right it looked like a twin turboprop. I suspect it was an medium large transport or something similar due to the shape, size, speed and smoke trail from the engines. I did not need to take evasive action to avoid hitting the aircraft. When I spotted the aircraft I called it to the first officer's attention and asked that he question the tower. Tower replied, 'oh, yes, I see it. 1-2 O'clock, less than a mi, altitude 1600 or 1700' climbing.' at the gate while passenger were deplaning, 1 passenger even commented. He asked if I had seen the aircraft that departed teterboro airport. I called ewr tower by phone. He was unaware of the aircraft until we called it. He said teb was running 1 to 1-1/2 hour ground delays and suspected this aircraft elected to cancel and depart VFR. They are supposed to stay low out of the TCA until well west, then climb. He estimated the aircraft about 7 or so mi south of teb placing it well into the TCA. I tried calling teb tower to talk with them but got no answer. I then passed all the information on to our system control to log the information. I'm all for going VFR if you can, but not to cause a hazard to other aircraft. ATC delays in congested areas are truly unacceptable, too high. This is causing frustration to the point where this aircraft seems to have attempted to 'beat the system.' I didn't like it much to say the least.

Related reports:

Google
 

Original NASA ASRS Text

Title: CLOSE PROX ACR-MLG ACR-MDT IN OR NEAR N90 TCA.

Narrative: ON APCH TO RWY 22L AT EWR. PASSING APPROX 1800' MSL ON G/S I SPOTTED FLASHING LIGHTS AHEAD, SLIGHTLY LEFT OF THE NOSE AND SLIGHTLY LOWER THAN OUR ACFT. AS IT MOVED ACROSS OUR FLT PATH, I COULD THEN SEE AND REALIZED IT WAS ANOTHER ACFT. AS IT MOVED TO THE RIGHT IT LOOKED LIKE A TWIN TURBOPROP. I SUSPECT IT WAS AN MLG OR SOMETHING SIMILAR DUE TO THE SHAPE, SIZE, SPD AND SMOKE TRAIL FROM THE ENGS. I DID NOT NEED TO TAKE EVASIVE ACTION TO AVOID HITTING THE ACFT. WHEN I SPOTTED THE ACFT I CALLED IT TO THE F/O'S ATTN AND ASKED THAT HE QUESTION THE TWR. TWR REPLIED, 'OH, YES, I SEE IT. 1-2 O'CLOCK, LESS THAN A MI, ALT 1600 OR 1700' CLBING.' AT THE GATE WHILE PAX WERE DEPLANING, 1 PAX EVEN COMMENTED. HE ASKED IF I HAD SEEN THE ACFT THAT DEPARTED TETERBORO ARPT. I CALLED EWR TWR BY PHONE. HE WAS UNAWARE OF THE ACFT UNTIL WE CALLED IT. HE SAID TEB WAS RUNNING 1 TO 1-1/2 HR GND DELAYS AND SUSPECTED THIS ACFT ELECTED TO CANCEL AND DEPART VFR. THEY ARE SUPPOSED TO STAY LOW OUT OF THE TCA UNTIL WELL W, THEN CLB. HE ESTIMATED THE ACFT ABOUT 7 OR SO MI S OF TEB PLACING IT WELL INTO THE TCA. I TRIED CALLING TEB TWR TO TALK WITH THEM BUT GOT NO ANSWER. I THEN PASSED ALL THE INFO ON TO OUR SYS CTL TO LOG THE INFO. I'M ALL FOR GOING VFR IF YOU CAN, BUT NOT TO CAUSE A HAZARD TO OTHER ACFT. ATC DELAYS IN CONGESTED AREAS ARE TRULY UNACCEPTABLE, TOO HIGH. THIS IS CAUSING FRUSTRATION TO THE POINT WHERE THIS ACFT SEEMS TO HAVE ATTEMPTED TO 'BEAT THE SYS.' I DIDN'T LIKE IT MUCH TO SAY THE LEAST.

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