Jump to content

Andrew Heath

Network Directors
  • Posts

    1,327
  • Joined

  • Last visited

  • Days Won

    132

Everything posted by Andrew Heath

  1. Andrew Heath

    NEW YORK CENTER

    until
    Sector: KZNY.ZNY.B.56Booking for KZNY.ZNY.B.56 created on the POSCON HQ.
  2. Andrew Heath

    NEW YORK CENTER

    until
    Sector: KZNY.ZNY.B.56Booking for KZNY.ZNY.B.56 created on the POSCON HQ.
  3. Andrew Heath

    Meetings

    Management Policy: 1.4.0 A Director/Manager meeting should be held once per calendar month. When a meeting is held, an agenda must be created and distributed at least 24 hours prior to the meeting to all applicable staff members. Meetings must have one person designated as the secretary to document the meeting discussion. At the conclusion of the meeting, the meeting minutes must be posted in the staff pages.
  4. We call "must" and "must not" words of obligation. "Must" imposes an obligation on the readers to tell them something is mandatory. "Must not" are used to say something is prohibited. While "shall" and "shall not" are not the most suitable terms for obligation, if you see the terms used in these policies, they have the same meaning as "must" and "must not". "May" means purely optional and does not imply that the writer recommends that option to the reader. "Should" also means optional but implies that the writer recommends and advises the reader to use that option. Summary: Must = mandatory Must not = prohibited May = optional Should = recommended These are the only valid word choices to convey those meanings.
  5. Management Policy: 1.5.0 Any vacant position that normally reports to a specific Director or Manager shall be assumed by that respective Manager or Director until filled.
  6. Management Policy: 1.0.0 Reserved
  7. Management Policy: 1.2.0 Reserved
  8. Management Policy: 1.6.0 Any person wishing to obtain a position that contributes Work Product to the POSCON Non-Profit Organization (POSCON Inc.) is required to sign the Volunteer Agreement. This includes, but is not limited to the following positions: President Network Directors Network Managers Division Managers Sub-Division Managers Moderators Support Specialists
  9. Management Policy: 1.1.0 The following staff positions require candidates to be 21 years of age or older on the day they assume the position: Network Directors Network Managers Division Managers Sub-Division Managers Moderators Support Specialists All other staff positions require candidates to be 18 years of age or older on the day they assume the position.
  10. Management Policy: 1.3.0 Only one staff position may be held by one individual at any given time on the POSCON Network. Exceptions may be granted on a case-by-case basis at the discretion of the President.
  11. Any point deduction can be appealed by going to your user profile and clicking on the “appeal” button next to the associated point loss. A word of warning though – you must have a valid reason to appeal a point deduction such as landing at a special airport (e.g. Paro Bhutan) that required a higher than normal descent rate in order to clear obstacles. If your reason is determined to be invalid, Moderators have the ability to deduct additional points as a punitive measure to discourage unwarranted appeals in the future.
  12. The following policies apply at the time of connection and/or during all times while connected to the Positive Control Network. Pilot Policy: 1.1.0 Pilot Policy: 1.1.1 Pilot Policy: 1.1.1 Pilot Policy: 1.1.2 Pilot Policy: 1.1.3 Pilot Policy: 1.1.4 Pilot Policy: 1.1.5 Pilot Policy: 1.1.6 (Not currently implemented) Pilot Policy: 1.1.7 Pilot Policy: 1.1.8 Pilot Policy: 1.1.9 Pilot Policy: 1.1.10 (Not currently implemented) Pilot Policy: 1.1.11 Pilot Policy: 1.1.12 Pilot Policy: 1.1.13
  13. Andrew Heath

    Pre-Flight

    The following policies apply to every time a pilot intends to fly on POSCON. Pilot Policy: 1.0.0 Pilot Policy: 1.0.1 Pilot Policy: 1.0.2 Pilot Policy: 1.0.3 (Not currently implemented) Pilot Policy: 1.0.4
  14. The following policies apply to all operations that are conducted at an Uncontrolled Airfield or in Uncontrolled Airspace. Pilot Policy: 3.2.0 Pilot Policy: 3.2.1
  15. The following policies apply to all operations that are conducted at a Controlled Airfield or in Controlled Airspace. Pilot Policy: 3.1.0
  16. The following policies apply to all operations. Pilot Policy: 3.0.0 Pilot Policy: 3.0.1 Pilot Policy: 3.0.2 Pilot Policy: 3.0.3 Pilot Policy: 3.0.4
  17. The following policies apply to flight operations that are conducted at an Uncontrolled Airfield or in Uncontrolled Airspace. Pilot Policy: 2.5.0 Pilot Policy: 2.5.1
  18. The following policies apply to flight operations that are conducted at a Controlled Airfield or in Controlled Airspace. Pilot Policy: 2.4.0 Pilot Policy: 2.4.1
  19. The following policies apply to all flight operations. Pilot Policy: 2.3.0 Pilot Policy: 2.3.1 Pilot Policy: 2.3.2 Pilot Policy: 2.3.3 (Not currently implemented) Pilot Policy: 2.3.4 (Not currently implemented) Pilot Policy: 2.3.5 (Not currently implemented) Pilot Policy: 2.3.6 (Not currently implemented) Pilot Policy: 2.3.7 (Not currently implemented) Pilot Policy: 2.3.8 (Not currently implemented) Pilot Policy: 2.3.9 (Not currently implemented) Pilot Policy: 2.3.10 Pilot Policy: 2.3.11 Pilot Policy: 2.3.12
  20. The following policies apply to ground operations that are conducted at an Uncontrolled Airfield or in Uncontrolled Airspace. Pilot Policy: 2.2.0
  21. The following policies apply to ground operations that are conducted at a Controlled Airfield or in Controlled Airspace. Pilot Policy: 2.1.0 Pilot Policy: 2.1.1 Pilot Policy: 2.1.2
  22. The following policies apply to all ground operations. Pilot Policy: 2.0.0 Pilot Policy: 2.0.1 Pilot Policy: 2.0.2 Pilot Policy: 2.0.3
  23. Policies that are adopted need to be constantly evaluated by both the staff and membership to ensure that they remain relevant. Policies can and should evolve over time based on feedback from the membership. If something doesn't work well for you, we want to hear about it! Your input is critical to the success of POSCON so we encourage you to submit your policy suggestions. You can do this publicly or privately at your discretion. For public policy feedback, feel free to use our Feature Requests section of our Forum. For private policy feedback, feel free to email [email protected]
  24. The following outlines a general flow for how Feedbacks are reviewed.
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and Guidelines.