Originally Posted by
Check Airman
Are we sure this notification was made 40 mins prior? From the audio, it sounded like they were talking to the approach controller, which would’ve been more like 40 miles than 40 minutes.
Assuming the video and the LiveATC mashup is accurate: the video first has the DLH say they’re unable “visual approaches” at night at around 13,500ft. With a timestamp added of 0345z at 11,000ft the controller and pilot confirm it’s “visual separation” at night that’s the issue. The video and timestamp then runs on, and at 0421z still at 11,000ft is when the DLH says they need a base soon or it’ll mess up the sequence, then shows as 0422z when the controller refuses to update the delay. Admittedly that’s 37 minutes, but it rounds up close enough if you add the other 2,500ft of descent. I’m assuming it wasn’t 40 minutes before their original slot in the sequence, but it’s the best part of 40 minutes notice in which to generate a gap.