how add aircraft to acft.Code when filing PIREP...
3 years 5 months ago #17183
by BillMan4
how add aircraft to acft.Code when filing PIREP... was created by BillMan4
When I file my PIREP and get to the entry for acft.Code I can't find the aircraft listed that I'm flying, i.e. Cessna 152, Cessna 172, etc. So I always end up selecting "ANY". Am I doing something wrong or is there a way to add the aircraft to the list of choices? NOTE: Am not trying to make any more work for anyone just wondering if there is something I'm missing when I file the PIREP. Any info would be appreciated.
PILOT ID: 697
PILOT ID: 697
Please Log in to join the conversation.
3 years 5 months ago - 3 years 5 months ago #17184
by SPA118
Replied by SPA118 on topic how add aircraft to acft.Code when filing PIREP...
You're correct by selecting "ANY" when you file your PIREP. Sometimes for my own records I will put the type of aircraft I'm flying in the remarks section of ACARS or in the notes section when manually filing a PIREP.
Last edit: 3 years 5 months ago by SPA118.
The following user(s) said Thank You: BillMan4
Please Log in to join the conversation.
3 years 5 months ago #17185
by jer029
Replied by jer029 on topic how add aircraft to acft.Code when filing PIREP...
Eric is correct. SPAACARS will put the aircraft type in the pirep but manual pirep will not. Those types that are available were hard coded in and must be updated the same way. Not high on my priority list, as SPAACARS is the preferred method for of pirep filing.
Manual pirep entry is legacy pirep entry for pilots who couldn’t use FSACARS and the later SPAACARS. It remains available for that same reason, but it is more limited than FSACARS and our current version of SPAACARS.
Happy flying,
John
Manual pirep entry is legacy pirep entry for pilots who couldn’t use FSACARS and the later SPAACARS. It remains available for that same reason, but it is more limited than FSACARS and our current version of SPAACARS.
Happy flying,
John
The following user(s) said Thank You: BillMan4
Please Log in to join the conversation.
Time to create page: 0.065 seconds