I use flight notification (text message) as a form of validation that my filed flight plan made it to the FAA system; I’ve noticed that frequently the ETA on the text message is significantly different than what was filed. Case in point: N851SB from KCTJ to KRPH yesterday (4/27). Filed ETD was 1630 EDT (2030Z) and ETE was 2:40 (making the ETA for KRPH 2310Z or 1810 CDT. The text notification (unfortunately I already deleted it so am going from memory here) showed my proposed ETD as 1640 EDT and my proposed ETA as 1604 CDT – I wish we had that kind of cruise speed!
Here is a ‘snip’ from the filed plan off of FltPlan.com:
N851SB IFR GenAv TBM8/L Equip: DGLOVWZ/S
Dep: KCTJ 2030Z 310kts FL280 Filed Route
2 questions -
why the 10 minute slip in proposed ETD? I have noticed that is often the case (but not always)
why the significant discrepancy in ETA? Very common to observe that.
The Enhanced Traffic Management System usually adds 10 minutes to departure times (plus any expected delays).
The NAS flight plan came in with a 04/27/09 20:30:00 EDT and 0240 ETE, but ETMS decided you’ll depart at 04/27/09 20:40:00 and arrive at 04/27/09 21:04:00. You departed at 04/27/09 20:51:00 and at that time they estimated your arrival at 04/27/09 21:13:00, another 2 minute reduction in ETE. Then ETMS stopped sending messages about your flight, so all we got were the NAS messages which don’t include an ETA or ETE. ETMS may have been indicating the time they expected to stop sending messages about your flight, but I don’t know why your flight wouldn’t be generating ETMS messages.