Consistency in approval standards: one manager might opt to allow a PIREP that arrived unusually early, while another might not.
What if a set standard was adhered to? What if there were written guidelines about delayed/early flights?
Because each flight is different in its own way whether it's wind patterns, the aircraft type or the length or the flight. You can't write a set of guidelines for each and every flight, neither can you set rules for groups of flights.
Consistency in approval time: one manager might approve PIREPs every day, while another might take longer.
What if every VA Manager had a, say, weekly, pre-arranged quota he was ready and committed to adhere to?
The fact of the matter is half of the are busy, have other life commitments and don't need more things to do so they aren't available as often.
I reckon if there was a survey of Management, half of them would say they don't have enough time to dig through PIREPS.
Better treatment of returning pilots: pilots that flew with us in the past often don't mention that they previously flew for us, so they don't request that those hours be credited. My memory is good at recognizing names, and has let to hours credited for pilots that haven't flown for us in years.
I'm sure there are 'regulars' who file PiREPs more often than others. These would probably be easily recognisable after reviewing a few of their PiREPs. For the other, less recognisable ones, all it takes is a Word (or even Notepad, lol) document, ctrl+f, and their surname being typed to find out (a task completed in mere seconds)
I think you've misunderstood, Aaron is talking about when a pilot gets taken off the roster (with say 500 hours) and then comes back two years later and files a PIREP, when Aaron spots someone who has returned or they say so in the comments they will recieve 500 hours. And since all of you people are so frightened that you'll get taken off the roster, it's obviously a big deal for them.
Maintain database integrity and security: PIREP approval often requires database access to edit or delete PIREPs. This can be complicated to do and also raises security risks.
I understand and agree with this point, but isn't it each pilot's responsibility to edit rejected PiREPs? I know I still have 8 PiREPs "requiring modification", all from my first couple weeks' or so's membership, which I still don't know what to do with actually... lol
Editing, that's the pilot's job.
What about deleting? Who does that? Aaron (or the manager, if this gets put in place)
Schedule knowledge: SimAirline.net's airlines fly over 20,000 flights per day. While it's impossible to know all of the schedules, it is possible to tell quickly if a PIREP has an obvious problem. This is the goal of checking PIREPs, and it's difficult to pass this skill (acquired over the last nine years) on.
I'm in admiration of this knowledge. Impressive (not sarcastic btw). How many digits of Pi can you recite?
However, is there really that much of a difference between typing a few figures and airport codes into a database, and knowing them off by heart? The time difference is surely negligeable, a matter of seconds?
Again, it comes down to time.
We are going to use a couple of management as an example and Feburary's Statistics.
The amount of PIREPs to approve/disapprove: (the amount of airlines they have)
Gregg James(3): 364
Alex Sanins(2): 206
Victor Meurtrier(1-delta): 426
We haven't taken into account people's personal lives and other commitments.
I did a wee trial, and for a random flight from Johannesburg to London heathrow it took about 30 seconds to look it up and compare. 30 seconds each PIREP +/- 10 seconds with the odd one that goes faster or slower, you do the math, it's going to take quite a while to approve all of them on top of other management duties and other commitments.
1) Some managers down't know the routes enough to know whether it's a discontinued flight or not. For most virtual airlines it would require searching the in our timetable and the electronic timetable to figure it out.
2)There's a thing with travel timetables that you can't search into the past without going into the future. Say I try and search JNB-LHR on 1/1/09 on the Star Alliance timetable, when I look at the date it says "Janurary 1 2010" - and that isn't what I want. And timetables don't include the past in their databases, if I set my system date back to 1/1/09, it comes up with: "This City Pair is served, but the flight server did not find any logical connections (1 January 2009)"
This is where Aaron comes in handy
Carlo, you have some good points, and it would be exciting if we could approve PIREPs.
But I'm not sure if I should be using the little time I have that way.
At the moment I have three painting porjects on the go and one model (this'll be kept a secret for now
), a c***load of homework and life to deal with.
*Holy moly that took awhile. Carlo don't do this to me again!