Airspace Infringement
Join Date: Jun 2002
Location: Southern Europe
Posts: 318
Likes: 0
Received 0 Likes
on
0 Posts
Sidestick
If not done already, check with maintenance to try to obtain/retreive any FDM records about this flight, and try to obtain as much info as possible about how the SID was done. 6 months later is a bit hard to remember.
NOT saying that it was not done at the time, but check with operations and try to retreive your dispatch paperwork for that flight, and go through the NOTAMs very in detail. See if, at the time, there was any Notam about the SID that you did. Check also the SID applicable at the time.
I was thinking more in the lines of a possible Altitude Constraint, or something similar, but if you say that it might be noise, well people tend to forget that aircraft DO make noise. A heavy payload on that day ?
Very Correct ! Can not over emphasize the importance of this.
On this subject, years ago did some ad-hoc flights to AMS. Remember a specific notam about an SID out of AMS mentioning a bad FMS database for that specific SID which would result in a Deviation from the SID. Probably some deviations happened. The issue was reviewed, the cause was established that the Database was incorrect for that SID, and the Correct thing was done by publishing a Notam advising about it, instead of, you deviated, so I have a nice fine for you.
A wrong database would be now impossible to prove, as that database is long gone.
All the best and Thanks for sharing the event.
If not done already, check with maintenance to try to obtain/retreive any FDM records about this flight, and try to obtain as much info as possible about how the SID was done. 6 months later is a bit hard to remember.
NOT saying that it was not done at the time, but check with operations and try to retreive your dispatch paperwork for that flight, and go through the NOTAMs very in detail. See if, at the time, there was any Notam about the SID that you did. Check also the SID applicable at the time.
I was thinking more in the lines of a possible Altitude Constraint, or something similar, but if you say that it might be noise, well people tend to forget that aircraft DO make noise. A heavy payload on that day ?
On this subject, years ago did some ad-hoc flights to AMS. Remember a specific notam about an SID out of AMS mentioning a bad FMS database for that specific SID which would result in a Deviation from the SID. Probably some deviations happened. The issue was reviewed, the cause was established that the Database was incorrect for that SID, and the Correct thing was done by publishing a Notam advising about it, instead of, you deviated, so I have a nice fine for you.
A wrong database would be now impossible to prove, as that database is long gone.
All the best and Thanks for sharing the event.
Join Date: Mar 2001
Location: I wouldn't know.
Posts: 4,497
Likes: 0
Received 0 Likes
on
0 Posts
Denti : you are correct in affirming that the PIC is responsible but later, suggest passing the buck to the FMC provider. Can't pass the buck I suggest. Doesn't matter who is flying the aircraft and SOP's these days will often dictate that automatics are engaged. If P2 is handling and or automatjics are handling, PIC remains PIC and responsible.
