2009-11 · NASA ASRS report 862870
Air Carrier departure from MIA experienced TCAS TA that developed into a conflict with a VFR overflight. Reporter questions ATC's approval of the VFR transition aircraft and the spacing judgment utilized.
Departing MIA on the WINCO1 RNAV Departure; we were 15 miles East of BORLE Intersection and cleared to climb to 16;000 FT. As we were approaching 14;000 FT; Departure Control called out traffic at our 11 o'clock position and XX miles (don't remember distance but it was close to us) at 16;000 FT. I called him back to query the altitude of the traffic; he's at 16;000 FT? ATC said Yes; he's VFR...passing 14;500 FT I told him we wanted a different altitude to level off below the traffic. We got a TCAS TA calling out the VFR aircraft. ATC cleared us to level off at 15;000 FT; (all of this happened very quickly as we had been climbing out at approximately 2000 FT per minute). As we leveled off at 15;000 FT we both picked up the aircraft coming out of the glare from the sun at 11 o'clock and closing rapidly with us L to R. It looked like a light twin business jet (later ATC told us it was a Falcon 900); and it passed directly overhead of us at 16;000 FT. I told ATC that was very close; and that we were going to file a report. Even though we ultimately were separated by 1000 FT; had things transpired as cleared; it could have been much different. all of this happened very quickly. MIA Departure Control was quite busy with multiple aircraft on the frequency. Understanding that call outs of VFR traffic by ATC is on a workload permitting basis; we are very grateful that we had the extra seconds to make a decision before a midair collision or evasive action became necessary to avoid this VFR aircraft. Although the TCAS TA advisory initiated; acquiring the aircraft was very difficult due to sun angle and glare from clouds. Had the TA turned into an RA; it would have been; in my opinion a very aggressive transition to avoid the traffic (possibly causing injury to flight attendants in the main cabin). We were only a few links away in the 'chain of safety' from a midair collision. Not sure why a Falcon 900 was transiting and IFR Departure Corridor off of several busy major airports; and why it was level at 16;000 FT VFR.
During climb out of MIA; we were cleared to 16;000 FT. Passing about 14;000 FT departure reported traffic at 11 o'clock; 6 miles at 16;000 FT. We were unable to see the other aircraft since it was directly in line with the sun. We questioned our original clearance to 16;000 FT then requested and received clearance to level at 15;000 FT. Just prior to level off at 15;000 FT; we got a TCAS 'alert' and a Falcon 900 passed overhead at 16;000 FT. The Falcon was VFR and not in contact with our Controller. When clear of traffic we continued our climb to altitude. If Approach Control did not call the traffic we would have only had TCAS to prevent an accident. We reported the incident to our Dispatch.
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.