Altitude Deviation FORM

Altitude Deviation FORM

<p> Altitude Deviation FORM</p><p>Report to SATMA of an altitude deviation of 300ft or more, including those due to TCAS, Turbulence and Contingency Events</p><p>1. Today’s date: 18/04/07 2. Reporting Unit: ACC-Dakar</p><p>DEVIATION details</p><p>3. Operator Name: KLM 4. Call Sign: 5. Aircraft Type: 6. Mode C Displayed: KLM791 B772</p><p>7. Date of Occurrence: 8. Time UTC: 9. Occurrence Position (lat/long or Fix): 18/04/07 10. Cleared Route of Flight: UN873</p><p>11. Cleared Flight Level: 12. Estimated Duration at Incorrect 13. Observed Deviation (+/-ft): 340 Flight Level (seconds): N. D. + 2000 FT 14. Other Traffic Involved: None</p><p>15. Cause of Deviation (brief title): </p><p>(Examples: ATC Loop Error, Turbulence, Weather, Equipment Failure) AFTER DEVIATION IS RESTORED</p><p>16. Observed/Reported Final Mark the appropriate box: 19. Did this FL comply Flight Level*: FL 340 (Pilot) with the ICAO Annex 2 Tables of Cruising 17. Is the FL above the cleared level: X Levels? *Please indicate the source of X Yes information – ModeC/Pilot 18. Is the FL below the cleared level: _ _ No</p><p>Narrative</p><p>20. Detailed Description of Deviation (Please give your assessment of the actual track flown by the aircraft and the cause of the deviation.)</p><p>This aircraft had been coordinated by SAL ACC.to Dakar ACC for FL340. The aircraft arrived there on FL360. crew comments (if any)</p><p>When complete please forward the report(s) to: South Atlantic Monitoring Agency (SATMA) E-Mail: [email protected] Altitude Deviation FORM</p><p>Report to SATMA of an altitude deviation of 300ft or more, including those due to TCAS, Turbulence and Contingency Events</p><p>1. Today’s date: 18/04/07 2. Reporting Unit: Dakar ACC </p><p>DEVIATION details</p><p>3. Operator Name: TAP 4. Call Sign: 5. Aircraft Type: 6. Mode C Displayed: TAP181 A332</p><p>7. Date of Occurrence: 8. Time UTC: 9. Occurrence Position (lat/long or Fix): 18/04/07 10. Cleared Route of Flight: UN741</p><p>11. Cleared Flight Level: 12. Estimated Duration at Incorrect 13. Observed Deviation (+/-ft): FL 380 Flight Level (seconds): N. D. + 2000 FT 14. Other Traffic Involved: None</p><p>15. Cause of Deviation (brief title): </p><p>(Examples: ATC Loop Error, Turbulence, Weather, Equipment Failure) AFTER DEVIATION IS RESTORED</p><p>16. Observed/Reported Final Mark the appropriate box: 19. Did this FL comply Flight Level*: FL400 (Pilot) with the ICAO Annex 2 Tables of Cruising 17. Is the FL above the cleared level: X Levels? *Please indicate the source of X Yes information – ModeC/Pilot 18. Is the FL below the cleared level: _ _ No</p><p>Narrative</p><p>20. Detailed Description of Deviation (Please give your assessment of the actual track flown by the aircraft and the cause of the deviation.)</p><p>This aircraft had been coordinated by SAL ACC. for Dakar ACC at 15H02 to KENOX. The aircraft arrived there at 15H07. crew comments (if any)</p><p>When complete please forward the report(s) to: South Atlantic Monitoring Agency (SATMA) E-Mail: [email protected] Altitude Deviation FORM</p><p>Report to SATMA of an altitude deviation of 300ft or more, including those due to TCAS, Turbulence and Contingency Events</p><p>1. Today’s date: 18/04/07 2. Reporting Unit: Dakar ACC</p><p>DEVIATION details</p><p>3. Operator Name: AFR 4. Call Sign: 5. Aircraft Type: 6. Mode C Displayed: AFR456 A332</p><p>7. Date of Occurrence: 8. Time UTC: 9. Occurrence Position (lat/long or Fix): 18/04/07 10. Cleared Route of Flight: </p><p>11. Cleared Flight Level: 12. Estimated Duration at Incorrect 13. Observed Deviation (+/-ft): FL 380 Flight Level (seconds): N. D. + 2000 FT 14. Other Traffic Involved: None</p><p>15. Cause of Deviation (brief title): </p><p>(Examples: ATC Loop Error, Turbulence, Weather, Equipment Failure) AFTER DEVIATION IS RESTORED</p><p>16. Observed/Reported Final Mark the appropriate box: 19. Did this FL comply Flight Level*: FL400 (Pilot) with the ICAO Annex 2 Tables of Cruising 17. Is the FL above the cleared level: X Levels? *Please indicate the source of X Yes information – ModeC/Pilot 18. Is the FL below the cleared level: _ _ No</p><p>Narrative</p><p>20. Detailed Description of Deviation (Please give your assessment of the actual track flown by the aircraft and the cause of the deviation.)</p><p>This aircraft had been coordinated by SAL ACC. for Dakar ACC at 14H29 to KENOX. The aircraft arrived there at 14H35.</p><p> crew comments (if any)</p><p>When complete please forward the report(s) to: South Atlantic Monitoring Agency (SATMA) E-Mail: [email protected] </p><p>Send to SATMA Fax: +34 928 577052 E-Mail: [email protected]  SATM A</p><p>Type of Report: x PILOT – Flight x CONTROLLER – ATC Unit Type of Error: x LATERAL  Type (A to G) (*) Date/Time (UTC): 26/04/07 11h33 Causes: x  WEATHER (See G)  OTHERS (Specify)</p><p>Conflict Alert Systems:</p><p>DETAILS OF AIRCRAFT FIRST Aircraft Aircraft Identification : N468AB Name of Owner/Operator : Aircraft Type : GLF4 Departure Point : GVAC Destination : SBFZ Route Segment : POMAT-NELTO-DEKON</p><p>Cleared Actual Flight Level: 400 400 Cleared Track: UN741 Extent of deviation - magnitude and direction: (NM for lateral) 100NM Position where deviation was observed: POMAT (BRG/DIST from fixed point or LAT/LONG) Action Taken by ATC/Pilot:</p><p>Other comments: Coordinated at KENOX, the aircraft reports at POMAT next NELTO and DEKON. SAL apologizes for this situation.</p><p>(*) See deviation classification </p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    4 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us