A VFR PA-28 pilot was advised after a cross country that flight service was looking for him because ...

Attributes
ACN	1162023
Time
Date	201404
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	Parked
Route In Use	Direct
Flight Plan	VFR
Component
Aircraft Component	Electronic Flt Bag (EFB)
Person 1
Function	Single Pilot Pilot Flying
Qualification	Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Instrument
Experience	Flight Crew Last 90 Days 22 Flight Crew Total 883 Flight Crew Type 115
Events
Anomaly	Deviation - Procedural Published Material / Policy Deviation - Speed All Types

Narrative:

I filed and flew two VFR out and back legs. I planned the flight on my ipad using garmin pro pilot; but filed using [a flight planning website]. I had just landed at my home airport and was putting the aircraft in the hangar when a car drove up and the driver asked if I had a VFR flight plan. I replied in the affirmative; and stated that I had just landed and was about to close it. The driver said that the FSS had called the airport and was looking for me. I immediately closed the flight plan; but I was puzzled as to why this had occurred. Upon arrival back home; I looked at the filing. The online software automatically populates the speeds for aircraft type; while the pilot enters the other data. The software [I] had used the correct airspeed for the first leg; but then used an airspeed 25 KTS faster for the second leg. Because I was using the ipad enroute; I didn't catch the discrepancy. I am going to be much more cautious about automatic online filing; and review each item more closely. It is my fault that this occurred. The FSS was right to check on me; and I'm grateful they did.

Original NASA ASRS Text

Title: A VFR PA-28 pilot was advised after a cross country that Flight Service was looking for him because he was overdue. Upon investigating; the pilot determined that the return leg speed the iPad software calculated; and he then filed for; was higher than normal speed for his aircraft type.

Narrative: I filed and flew two VFR out and back legs. I planned the flight on my iPad using Garmin Pro Pilot; but filed using [a flight planning website]. I had just landed at my home airport and was putting the aircraft in the hangar when a car drove up and the driver asked if I had a VFR flight plan. I replied in the affirmative; and stated that I had just landed and was about to close it. The driver said that the FSS had called the airport and was looking for me. I immediately closed the flight plan; but I was puzzled as to why this had occurred. Upon arrival back home; I looked at the filing. The online software automatically populates the speeds for aircraft type; while the pilot enters the other data. The software [I] had used the correct airspeed for the first leg; but then used an airspeed 25 KTS faster for the second leg. Because I was using the iPad enroute; I didn't catch the discrepancy. I am going to be much more cautious about automatic online filing; and review each item more closely. It is my fault that this occurred. The FSS was right to check on me; and I'm grateful they did.

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.

A VFR PA-28 pilot was advised after a cross country that flight service was looking for him because he was overdue. Upon investigating; the pilot determined that the return leg speed the ipad software calculated; and he then filed for; was higher than normal speed for his aircraft type.