A pilot filing an IFR flight plan revision because of an aircraft change discovered that incorrect i...

Narrative:

This report was to alarm all those in regulatory position of a potential concern with filing flight plans when you have a user profile on file with FSS. On nov/xa/08 I had filed to fly IFR in a piper warrior. Due to a mechanical issue we opted to take my aircraft. I explained to the briefer that I already had an IFR flight plan filed and briefing but needed to amend or create a new flight plan due to an aircraft change. The briefer pre-populated my information based on my stored cell phone number. Rather than a going block by block in the flight plan sequence the briefer asked me to fill in gaps. However; there were certain elements such as equipment type that had changed from standard. In addition; my alternate airport selection which was not entered. I was able to later amend this information and there were no further problems. There was no major issue this day however; it appears that the user profile system with FSS might lead pilots to think they are all set but in reality take off with incorrect or missing information due to a joint effort to expedite the filing of a flight plan. Let's remember that this can result in a violation of a far but more importantly result in an issue of safety.

Original NASA ASRS Text

Title: A PILOT FILING AN IFR FLIGHT PLAN REVISION BECAUSE OF AN AIRCRAFT CHANGE DISCOVERED THAT INCORRECT INFORMATION CAN INADVERTENTLY BE INCLUDED OR EXCLUDED THAT MAY VIOLATE FAR'S WHEN A FSS BRIEFER ENTERS PRE-POPULATED DATA.

Narrative: THIS RPT WAS TO ALARM ALL THOSE IN REGULATORY POS OF A POTENTIAL CONCERN WITH FILING FLT PLANS WHEN YOU HAVE A USER PROFILE ON FILE WITH FSS. ON NOV/XA/08 I HAD FILED TO FLY IFR IN A PIPER WARRIOR. DUE TO A MECHANICAL ISSUE WE OPTED TO TAKE MY ACFT. I EXPLAINED TO THE BRIEFER THAT I ALREADY HAD AN IFR FLT PLAN FILED AND BRIEFING BUT NEEDED TO AMEND OR CREATE A NEW FLT PLAN DUE TO AN ACFT CHANGE. THE BRIEFER PRE-POPULATED MY INFO BASED ON MY STORED CELL PHONE NUMBER. RATHER THAN A GOING BLOCK BY BLOCK IN THE FLT PLAN SEQUENCE THE BRIEFER ASKED ME TO FILL IN GAPS. HOWEVER; THERE WERE CERTAIN ELEMENTS SUCH AS EQUIP TYPE THAT HAD CHANGED FROM STANDARD. IN ADDITION; MY ALTERNATE ARPT SELECTION WHICH WAS NOT ENTERED. I WAS ABLE TO LATER AMEND THIS INFO AND THERE WERE NO FURTHER PROBS. THERE WAS NO MAJOR ISSUE THIS DAY HOWEVER; IT APPEARS THAT THE USER PROFILE SYS WITH FSS MIGHT LEAD PLTS TO THINK THEY ARE ALL SET BUT IN REALITY TAKE OFF WITH INCORRECT OR MISSING INFO DUE TO A JOINT EFFORT TO EXPEDITE THE FILING OF A FLT PLAN. LET'S REMEMBER THAT THIS CAN RESULT IN A VIOLATION OF A FAR BUT MORE IMPORTANTLY RESULT IN AN ISSUE OF SAFETY.

Data retrieved from NASA's ASRS site as of May 2009 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.

Attributes
ACN	812293
Time
Date	200811
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Person 1
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi
Experience	flight time last 90 days : 70 flight time total : 1485 flight time type : 100
ASRS Report	812293
Events
Anomaly	non adherence : far
Independent Detector	other flight crewa other other : fss
Resolutory Action	other
Supplementary
Problem Areas	FAA
Primary Problem	FAA

A pilot filing an IFR flight plan revision because of an aircraft change discovered that incorrect information can inadvertently be included or excluded that may violate far's when a FSS briefer enters pre-populated data.