1. 1 Impact of data accuracy on TFM initiatives Fluctuation in demand leads to : –Fewer compressions –More revisions –Unnecessary extensions –Needless delay

2. 2 LGA 10/16 Example TMS actively managed program to deliver enough a/c TimeOperationStart TimeEnd TimeAAR 10:17Original GDP11:3017:5935 12:47Compression12:4417:59 14:03Extension18:0021:5935 15:10Revision14:4921:5935/40/32/32/32/32/32/32 18:00Extension22:001:5932 21:56Rev/Ext23:003:5935 22:27Rev23:003:5939 22:46Compression22:430:00 00:23GDP CNX

3. 3 GDP Deliver HourRate Tower Cnt 11003538+3 12003539+4 13003541*+6 14003543+8 150035,4034= 16003237+5 17003225-7 18003240+8 19003234+2 20003236+4 21003227-5 22003234+2 23003936-3 00003934-5 * includes double count for 3 go-arounds

4. 4 Prior to 1800 extension Arrival demand “a little light for 1700 hour” No action taken to increase so they could try to “get LGA out of their departure delays” Program delivering at AAR for rest of program hours Extension necessary

5. 5 1800 Plan - extension until 0159 Arrivals at or above AAR for next 4 hours Departures still backed up

6. 6 Just 45 minutes after 1800 plan 13 flights Departing Past EDT 8 out of 37 flights in 1900Z hour or 22% of flights departing late

7. 7 Dark-greenie Flight List

8. 8 Large spike of late departures Late departures spread out - looks okay Flights are drifting later in time Revision and extension indicated

9. 9 2231 Plan - revise at higher rate Rate raised to 39 Revision shifts flights later producing under delivery in 2200 hour 15 flights departing past EDT – 10 out of 42 in 2300Z (~24%).

10. 10 GDP CNX at 0023 Canceled prior to end time of 1800 extension 2156 extension was unnecessary

11. 11 Backup

12. 12 Prior to 1800 extension Arrival demand “a little light for 1700 hour” No action taken to increase so they could try to “get LGA out of their departure delays” Program delivering at AAR for rest of program hours Extension necessary

13. 13 1 hour after extension Demand above AAR Delivery fairly smooth Compression not indicated

14. 14 After modeled Compression Savings of 9 minutes on average delay Spike in demand in 20z No compression implemented

15. 15 2 hours after extension Compression is not indicated Revision is indicated

16. 16 After Modeled Compression Delay savings of 15 minutes Increased demand in 22 & 23 hours No compression this hour

17. 17 Delay savings by carrier if compression had been run hourly Jean, I don’t think the carrier stats are significant

18. 18 After modeled revision Demand at or below AAR from 2200 on Average delay 160 min No revision was run at this time

19. 19 4 hours after extension Revision indicated Extension also indicated

20. 20 After modeled compression Delay savings of 11 minutes, average 136 Increased demand in 2200 & 2300 hours No compression was run