View Single Post
Old 08-25-2010 | 02:19 PM
  #46084  
Dash8widget
Gets Weekends Off
 
Joined: Feb 2008
Posts: 467
Likes: 0
From: SLC ERB
Default

Originally Posted by acl65pilot
King, I know what you are getting at. Your point is all of that is in other places on the release. When I stared here, I was also a little surprised that all of that data was no on the rental agreement, but I am sure it is digitally store somewhere.

I know that at my previous company when a MEL was added or deleted we needed to get approval an annotate it on the flight release. No so here. We get approval, but it is not on the copy that goes out the door. I guess it is just different. Seems to work though.
When it comes the the actual dispatch release ONLY the following MUST be included:

Sec. 121.687 - Dispatch release: Flag and domestic operations.
(a) The dispatch release may be in any form but must contain at least the following information concerning each flight:
(1) Identification number of the aircraft.
(2) Trip number.
(3) Departure airport, intermediate stops, destination airports, and alternate airports.
(4) A statement of the type of operation (e.g., IFR, VFR).
(5) Minimum fuel supply.
(b) The dispatch release must contain, or have attached to it, weather reports, available weather forecasts, or a combination thereof, for the destination airport, intermediate stops, and alternate airports, that are the latest available at the time the release is signed by the pilot in command and dispatcher. It may include any additional available weather reports or forecasts that the pilot in command or the aircraft dispatcher considers necessary or desirable.



Everything else that we consider to be part of the "release" is just extra stuff added by the company. Now, that extra stuff - like MEL's - may be required by the FOM but its not part of the FAR required release data. This explains why there is such differences from company to company.