Corporate jet flight crew reported an NMAC during takeoff from MMU airport requiring evasive action.
Synopsis
Corporate jet flight crew reported an NMAC during takeoff from MMU airport requiring evasive action.
Narrative
I'll start by saying I believe there was a controller in training at the time of this occurrence. I say that because during our taxi in on the leg prior; we heard two different controllers on ground like when a supervisor overrides another controller on the same freq. This did not happen again that I recall; but thinking back; there could have been some distractions in the Tower when our takeoff clearance was given. Wind was out of the west around 10 knots. There were many smaller airplanes doing left traffic pattern work on Runway 31 during our takeoff. Around the time of our takeoff I heard the controller tell someone in the pattern to start a turn. The PF (pilot flying) performed a very nice static takeoff on Runway 23. After positive rate and gear retraction; we quickly were at 400' when the PF called for NAV mode on the flight guidance (Morristown 7 departure). I immediately noticed traffic off our right to be Aircraft Y in the left downwind for Runway 31; slightly above us. As we climbed; this traffic appeared extremely close and setup to t-bone us. I told the PF to the shallow the climb around 1;500' just as we got an RA to level off; followed by a 'monitor vertical speed' as I recall. I was fixated on the traffic but looked at my PFD briefly to notice a red target at our altitude; at our same location. We were at the same altitude when I lost sight of Aircraft Y; passed just behind us. We got up to 2;200; 'clear of conflict' and reported it to the controller. We then descended to 2;000' and continued the left turn to 160 deg heading per the Morristown 7 departure. Tower asked if we needed assistance and then passed us off to departure control. It was the closest RA I've experienced and really shook us up for a few minutes. Prior to takeoff we held short of the runway waiting for an IFR release nearly 20 minutes; why this controller felt he must thread the needle to get us out I don't know. We'd have gladly sat another 20 minutes to avoid an RA or worse. It was close. Spacing miss-judgement by Tower Controller If Tower gave us a no-delay clearance; we could have rejected it knowing we briefed a static takeoff. We were not given this that I recall. Perhaps if tower had assigned right hand traffic for 31 to those in the pattern; it could have been avoided.
Second reporter narrative
We took off on Runway 23 and were advised of Aircraft Y traffic on left downwind for Runway 31 (passes through the departure path of Runway 23). Once we rotated we saw Aircraft Y on TCAS and shortly after we got a traffic alert. At about 1;000' MSL the PM identified the traffic and we immediately got a TCAS RA. I responded to the RA; climbing above our clearance altitude of 2;000' and once clear of conflict returned to our heading and altitude. We were cleared for takeoff with traffic on downwind which was too close to the departure path for our runway. ATC should not have cleared us for takeoff with downwind traffic approaching the departure corridor. There needs to be increased spacing.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.