FAA wants to change the airline's schedules weeks in advance in the hopes of reducing delays and congestion. This is a fantasy given the amount of "day of" variance within our aviation system. This is variance ATC can't fix, which will make FAA's weeks in advance predictions and actions moot. As an example, my daughter flew from San Francisco to Amsterdam on Saturday. She was scheduled to depart at 2:55 PM, but actually departed at 4:21 PM, 1 hour and 26 minutes late. The SFO to AMS flight was scheduled to arrive in AMS at 10:20 AM, but actually landed at 11:59 AM, 1 hour and 39 minutes late, thus losing an additional 13 minutes above schedule after leaving the gate. While you can read the rest if interested in the particulars, the point is that there was no way for ATC to know about the 1 hour plus delay weeks in advance, and certainly nothing ATC could do "day of" to correct this problem. The result is that ATC's well planned "day of" operation would fail, since this is certainly not the only example of non-ATC delay variance yesterday. There is absolutely nothing ATC could have done with this scenario weeks in advance, or even "day of" to make it better. Conversely, the airlines could have taken "day of" actions to mitigate the delay to their passengers. 1. Sped up the Beijing flight enroute to reduce the scheduled block time of 11+55 by 15 to 20 minutes 2. Built a faster turn time to reduce the SFO gate time from 1+51 by 15 to 20 minutes 3. Sped up the Amsterdam flight enroute to reduce the scheduled block time of 10+55 by 15 to 20 minutes This would have improved the AMS arrival time by 45 minutes to 1 hour. And if the aircraft then sped up back to SFO, it would then be close to back on time. The cause of the late SFO departure was an aircraft swap with the inbound aircraft landing at 2:30 PM. The inbound departed Beijing at 5:12 PM, 13 minutes early, and landed into SFO at 2:30, 10 minutes late, 23 minutes longer than schedule. Michael xxxxxxxxxxxxxxxxxxxxx R. Michael Baiada cell - (303) 521-6047 [email protected] <mailto:[email protected]>
-------------------------------------------------------------------------- Revised: 20250507
You are receiving The Mifnet because you requested to join this list. The Mifnet is largely a labor of love, however the infrastructure isn't exactly cost-free. If you'd care to make a small contribution to the effort, please know that it would be greatly appreciated: https://wardell.us/url/mifbit All posts sent to the list should abide by these policies: 1) List members acknowledge that participation in Mifnet is a privilege--not a right. 2) Posts are always off the record, absent specific permission from the author. 3) The tone of discussions is collegial. 4) Posts are expected to be in reasonably good taste. 5) We discuss ideas and not personalities, and we don't speak ill of other Mifnet members. * The Mifnet WEB SITE is: https://www.mifnet.com/ * To UNSUBSCRIBE from this list at any time please visit: https://lists.mifnet.com/ OR: SEND THIS MESSAGE via email: [email protected]?subject=leave * Send Mifnet mailing list POSTS/SUBMISSIONS to: [email protected] * You may reach the person managing The Mifnet at: [email protected] * Please consider the DIGEST version of The Mifnet, which consolidates all list traffic into 1-3 messages daily. See instructions at: https://lists.mifnet.com/ * Manage your personal Mifnet SUBSCRIPTION at: https://lists.mifnet.com/ * For a list of all available Mifnet commands, SEND THIS MESSAGE via email: [email protected]?subject=help * View The Mifnet LIST POLICIES and PRIVACY POLICY at: https://mifnet.com/index.php/policies * View instructions for Mifnet DELIVERY PROBLEMS at: https://mifnet.com/index.php/delivery-problems * View The Mifnet LIST ARCHIVE at: https://lists.mifnet.com/hyperkitty/list/[email protected]/
