37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 345430 |
Time | |
Date | 199608 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : 3j7 |
State Reference | GA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl |
Operator | general aviation : personal |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise other other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 50 flight time total : 1300 flight time type : 300 |
ASRS Report | 345430 |
Person 2 | |
Affiliation | government : faa |
Function | other personnel other |
Qualification | other |
Events | |
Anomaly | inflight encounter : weather non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other other : unspecified |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We filed a VFR flight plan with mia FSS for mth direct to ahn. Upon departure, we asked ZMA for VFR flight following which was granted. We had estimated the trip time at 3 hours. However, ATC vectors and inclement WX extended the actual time. At approximately jax, we asked for and received an IFR clearance direct to ahn. We ran into additional poor WX, and upon advice of thunderstorms from ZTL, decided to terminate IFR and land at greensboro, GA. Upon landing, the FBO told us FSS was 'looking for us because we were overdue.' we called atl FSS and the specialist told us 'we knew you'd changed from VFR to an IFR flight plan but we didn't trust the system, so we initiated a phone search.' I'm not sure if ATC should have notified mia FSS when we received an IFR clearance. Next time we'll get an FSS on the radio and cancel our own flight plan if we switch from VFR flight following to an IFR clearance. One problem this could cause: confusion in the ATC system. This could cause cancellation of our IFR plan. The rule here seems to be a little confusing.
Original NASA ASRS Text
Title: AN SMA PLT CHANGED TO AN IFR FLT PLAN FROM A VFR FLT PLAN WHILE ENRTE WITHOUT CANCELING HIS VFR FLT PLAN WITH AN FSS. FAR VIOLATION. AN FSS SPECIALIST STARTED A 'PHONE SEARCH' AS HE WAS SUPPOSED TO DO.
Narrative: WE FILED A VFR FLT PLAN WITH MIA FSS FOR MTH DIRECT TO AHN. UPON DEP, WE ASKED ZMA FOR VFR FLT FOLLOWING WHICH WAS GRANTED. WE HAD ESTIMATED THE TRIP TIME AT 3 HRS. HOWEVER, ATC VECTORS AND INCLEMENT WX EXTENDED THE ACTUAL TIME. AT APPROX JAX, WE ASKED FOR AND RECEIVED AN IFR CLRNC DIRECT TO AHN. WE RAN INTO ADDITIONAL POOR WX, AND UPON ADVICE OF TSTMS FROM ZTL, DECIDED TO TERMINATE IFR AND LAND AT GREENSBORO, GA. UPON LNDG, THE FBO TOLD US FSS WAS 'LOOKING FOR US BECAUSE WE WERE OVERDUE.' WE CALLED ATL FSS AND THE SPECIALIST TOLD US 'WE KNEW YOU'D CHANGED FROM VFR TO AN IFR FLT PLAN BUT WE DIDN'T TRUST THE SYS, SO WE INITIATED A PHONE SEARCH.' I'M NOT SURE IF ATC SHOULD HAVE NOTIFIED MIA FSS WHEN WE RECEIVED AN IFR CLRNC. NEXT TIME WE'LL GET AN FSS ON THE RADIO AND CANCEL OUR OWN FLT PLAN IF WE SWITCH FROM VFR FLT FOLLOWING TO AN IFR CLRNC. ONE PROB THIS COULD CAUSE: CONFUSION IN THE ATC SYS. THIS COULD CAUSE CANCELLATION OF OUR IFR PLAN. THE RULE HERE SEEMS TO BE A LITTLE CONFUSING.
Data retrieved from NASA's ASRS site as of July 2007 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.