2001-03 · NASA ASRS report 505348
B737 CAPT COMPLAINT REGARDING EWR ATCT CTLR HANDLING OF TFC ON A VFR DAY WITH GUSTY SURFACE WINDS IN NOT PROVIDING ADEQUATE ACFT SEPARATION.
THE PROB AROSE DUE TO WX; RWY CONFIGN (SIRO) AND CAPACITY PROBS AT EWR. WX VFR/VMC. STRONG NORTHWESTERLY WINDS AT 20-23 KNOTS GUSTS 30-35 KTS. LIGHT/MOD TURBULENCE IN RADAR PATTERN; 10K AIRSPEED FLUCTUATIONS COMMON. 'APCH IN USE ILS 4R; CIRCLE TO LND RWY 29.' AFTER EXTENSIVE VECTORS; WE FLEW THE APCH. ON APPROX 2 MILE FINAL TO RWY 29 WE SAW A TURBO PROP ON SHORT FINAL. WE HAD NO PRIOR AWARENESS OF THIS TFC. WHEN THIS COMMUTER ('ACR Y') MISSED THE TURNOFF AT TXWY UNIFORM; WE WERE APPROX 200-300 FT ABOVE TOUCHDOWN. I DECIDED TO GAR TO PREVENT A RWY INCURSION. DURING THE GAR; IE 5-10 SECS INTO IT; THE PNF ANNOUNCED; 'WATCH OUT FOR THAT AIRPLANE.' I LOOKED UP FROM THE INSTRUMENTS AND SAW AN ACR Z B737; AT 11 O'CLOCK HIGH; HEADING NE. INSTINCTIVELY; I RETARDED THRUST SLIGHTLY AND LEVELED OFF; OR REDUCED CLB RATE TO EVADE THE ACR Z FLT AND INSURE THE MOST SEPARATION POSSIBLE IN THE CONFLICT. WE CLBED TO 1700 MSL PER TWR INSTRUCTIONS/CLRNC. SUBSEQUENTLY; WE ENTERED A VFR PATTERN; FOLLOWING A B737 BACK AROUND FOR ANOTHER LNDG ON RWY 29. SECOND LNDG NORMAL. AFTER; HOWEVER; WE EXITED AT TXWY BB; RETURNING SE BOUND ON TXWY W; WE HAD TO YIELD TO ANOTHER B737 WHICH HAD LANDED BEHIND US. LAHSO SIRO; THERE SEEMS TO BE AN APPARENTLY DANGEROUS TFC CONFLICT AT EWR. THIS SEEMS TO BE ALLOWED TO INCREASE CAPACITY WITHIN THIS SIRO CONFIGN THERE IS MINIMAL SEPARATION OR INADEQUATE SEPARATION OF TFC ON THIS PROC. TERMINOLOGY ON CIRCLE VERSUS VISUAL APCH. AS CREW; WE WERE NOT ADVISED TO FOLLOW OR 'SELF SPACE' OUR ACFT. SMALL ACFT VISIBILITY IN HIGH TASK LOAD. SMALL ACFT NOT HAVING A SEPARATE RWY. TCASII EQUIP WE RECEIVED NO TCAS WARNING OR CAUTION ON ACFT Z BECAUSE WE WERE AT LOW ALTITUDE. USE OF TCASII AT ALL ALTITUDES NEEDS TO BE CONSIDERED AS LONG AS LAHSO/SIRO IS ALLOWED BY ATC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT HE AND MANY OTHER ACR PLTS OPERATING OUT OF EWR ARE CONCERNED ABOUT THE ATCT TECHNIQUE USED TO SEPARATE TFC WHEN VISUAL APCHS ARE IN PROGRESS. THE USE OF CROSS RWY SIMULTANEOUS OPS IS DANGEROUS WHEN AN UNEXPECTED GAR; OR MISSED APCH; IS MADE ON THE CROSS RWY 29 WHEN TKOFS ARE BEING MADE ON RWY 4L. THE PLTS ARE OBLIGATED TO GAR IF THEIR WIND SHEAR WARNING SOUNDS OFF; OR ANOTHER ACFT HAS NOT CLRED THE RWY IN TIME FOR LNDG. HE FURTHER STATED THAT THE FAA MGMNT HAS SINCE LOOKED INTO THIS MATTER AND HAS TAKEN ACTION AGAINST THE CTLRS AND RECOMMENDED THAT SOME CHANGES BE MADE TO PROVIDE BETTER SEPARATION DURING VISUAL OPS. SUBSEQUENT CALLBACK REVEALED THE FOLLOWING INFO: RPTR STATED THAT HE WAS OPERATING A B737 AND THE TURBO PROP STILL ON HIS RWY 29; CAUSING HIS GAR; WAS A LOW WING TURBO PROP COMMUTER. HE ADVISED THAT THE ACFT ALARMED HIM THE MOST WAS THE B737 DEPARTING RWY 4L WHICH IS AN INTERSECTING RWY; CAUSING A LOSS OF SEPARATION WITH HIS ACFT ON GAR. HE BELIEVES THAT THIS IS UNACCEPTABLE SINCE CTLRS; OR PLTS DO NOT KNOW WHEN ANOTHER ACFT ON A CROSSING RWY WILL HAVE TO MAKE A GOING AROUND; MISSED APCH; OR RESPOND FOR A WIND SHEAR WARNING. HE STATED THAT LAHSO WAS NOT INVOLVED IN THIS INCIDENT. HOWEVER; SIRO WAS SINCE IT WAS SIMULTANEOUS INTERSECTING RWY OPS. HE FURTHER STATED THAT HE RECEIVED A MEMORANDUM THROUGH HIS COMPANY FROM THE TWR; SUBSTANTIALLY WORDED AS FOLLOWS: INVESTIGATION OF RPTR'S INCIDENT WAS CONCLUDED AS THE EWR PROCS MEET CURRENTLY ACCEPTABLE STANDARDS AND NO ACTION IS NECESSARY OR MANDATED. HOWEVER; EXTRA STEPS ARE BEING TAKEN TO BRIEF CTLR CREWS WEEKLY AND THIS PROC WILL BE A FOCUS OF MANUAL TRAINING. THEY AGREE THAT THIS IS NOT A PREFERRED METHOD OF OP; BUT IN A BUSY TRAFFIC ENVIRONMENT WHERE WE ASK PLTS AND CLTRS ALIKE TO OPERATE AT PEEK EFFICIENCY; WE CAN EXPECT EVENTS SUCH AS THIS ON OCCASIONS. HIS FINAL COMMENT WAS THAT HE HAD ADVISED HIS CHIEF PLT THAT HE DOES NOT WANT TO FLY INTO EWR UNTIL TFC CTL PROCS ARE CHANGED TO ASSURE SEPARATION AND NOT JUST 'HOPE FOR IT!'
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.