C172 pilot reported that search and rescue personnel were looking for them because their filed arriv...

Attributes
ACN	1419569
Time
Date	201701
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	VFR
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 28 Flight Crew Total 135
Events
Anomaly	Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence

Narrative:

I took off to fly a solo cross country with touch and goes [enroute]. I filed a VFR flight plan using the foreflight app. The app calculated my time enroute between the airports; and after takeoff I contacted [the] FSS and activated my flight plan. I continued to get flight following through ATC and the app was giving me information that was correcting for the winds. I was under the impression that while on the ground; the enroute time was corrected for my headwind. I later found during the cancellation of the flight plan on the ground that I was 45 minutes late at my time of arrival. Search and rescue procedures had been started due to the delay. While the foreflight app was giving me information with the winds correcting my ETA; I don't believe the app accounted for landing at each airport that was filed on the route. As to my understanding; the app assumes that with every point filed; airport or anything else; you are flying over it at cruise airspeed and not taking account for the time spent landing; taxiing and taking off at each airport.

Original NASA ASRS Text

Title: C172 pilot reported that search and rescue personnel were looking for them because their filed arrival time was delayed when he made some practice touch and goes enroute.

Narrative: I took off to fly a solo cross country with touch and goes [enroute]. I filed a VFR flight plan using the ForeFlight app. The app calculated my time enroute between the airports; and after takeoff I contacted [the] FSS and activated my flight plan. I continued to get flight following through ATC and the app was giving me information that was correcting for the winds. I was under the impression that while on the ground; the enroute time was corrected for my headwind. I later found during the cancellation of the flight plan on the ground that I was 45 minutes late at my time of arrival. Search and rescue procedures had been started due to the delay. While the ForeFlight app was giving me information with the winds correcting my ETA; I don't believe the app accounted for landing at each airport that was filed on the route. As to my understanding; the app assumes that with every point filed; airport or anything else; you are flying over it at cruise airspeed and not taking account for the time spent landing; taxiing and taking off at each airport.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.