DOCSLIB.ORG

7110.65T, Air Traffic Control

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

ORDER JO 7110.65T Air Traffic Organization Policy Effective Date: February 11, 2010 SUBJ: Air Traffic Control This order prescribes air traffic control procedures and phraseology for use by personnel providing air traffic control services. Controllers are required to be familiar with the provisions of this order that pertain to their operational responsibilities and to exercise their best judgment if they encounter situations not covered by it. Distribution: ZAT-710, ZAT-464 Initiated By: AJR-0 Vice President, System Operations Services RECORD OF CHANGES DIRECTIVE NO. JO 7110.65T CHANGE SUPPLEMENTS CHANGE SUPPLEMENTS TO OPTIONAL TO OPTIONAL BASIC BASIC FAA Form 1320-5 (6-80) USE PREVIOUS EDITION 2/11/10 JO 7110.65T Explanation of Changes Basic Direct questions through appropriate facility/service center office staff to the Office of Primary Interest (OPI) a. Chapter 1. Introduction, Section 1. General change cancels and incorporates NJO7110.508, Ground This section has been adjusted to follow guidance provided Traffic Movement, effective September 30, 2009. in Federal Aviation Administration Order 1320.1E. h. 3-9-1. DEPARTURE INFORMATION b. 1-1-8. PUBLICATION AND DELIVERY This change will amend current guidance and provide DATES, and 1-1-10. CONSTRAINTS GOVERNING consistency with phraseology/procedures identified in SUPPLEMENTS AND PROCEDURAL paragraph 3-7-2. DEVIATIONS i. 3-9-9. TAKEOFF CLEARANCE An address change has been made for the military This change corrects an error in the placement of example headquarters, U.S. Navy. phraseology within the paragraph. This change cancels and c. 1-2-1. WORD MEANINGS incorporates N JO 7110.506, Takeoff Clearance, effective July 31, 2009. In compliance with FAA Order 1000.36, chapter 2, paragraph 1h, this change adds the definition of “must” to Also, adds “USAF” to paragraph 3-9-9e. This change the word meanings section in this directive. provides a source document for the USAF/ANG/AFRC d. 1-2-6. ABBREVIATIONS, and requirement to issue wind information in conjunction with 9-8-1. GENERAL a takeoff clearance. HQ Air Force Flight Standards Agency (AFFSA) has included the verbiage “RUNWAY (number)” This change corrects one of the organizations to which to the current prescribed phraseology to eliminate the UFO/unexplained phenomena activity can be reported. possibility of a controller not issuing the runway identifier NIDS is defunct and has been replaced by BAASS as the in conjunction with the takeoff clearance. This phraseo­ proper reporting agency. This change also includes a phone logy also standardizes the requirement throughout all number and e-mail address for BAASS. military services. e. 2-1-28. RVSM OPERATIONS j. 3-10-5. LANDING CLEARANCE This change adds language to list specific aircraft types of Requiring controllers to state runway identifier informa­ DOD-certified aircraft used by NASA that meet the tion in conjunction with all landing clearances mirrors the RVSM exception criteria. This change cancels and requirement specified in N JO 7110.487 dated August 11, incorporates NJO 7110.507, Reduced Vertical Separation 2008, for takeoff clearances. In addition, personnel at HQ Minimum (RVSM) Exceptions and Department of AFFSA request to add “USAF” to paragraph 3-10-5e to Defense (DOD)-Certified Aircraft, effective align with the requirements identified in paragraph 3-9-9a July31,2009. of the same order. This change provides a source document f. 2-7-2. ALTIMETER SETTING ISSUANCE for the USAF/ANG/AFRC requirement to issue wind BELOW LOWEST USABLE FL information in conjunction with all landing clearances. This phraseology example standardizes the requirement The change in phraseology provides the latest reported throughout all military services. altimeter setting and advises that it is more than one hour k. 4-2-5. ROUTE OR ALTITUDE old. Phraseology for issuing a standard altimeter setting is AMENDMENTS also added. g. 3-7-1. GROUND TRAFFIC MOVEMENT This change adds the notation “(ATC)” as it relates to ATC required altitude and/or speed restrictions on published The new paragraph b states, “do not issue unconditional procedures. When more than one altitude is charted on a instruction when authorizing movement on a runway/taxi­ procedure, the altitude without (ATC) annotated is for way for the purpose of airfield checks or other airport obstacle clearance, NAVAID, and/or communications operations.” The changes to subparagraph d, note 2, clarify reception and must be complied with and cannot be that “declared distances” used by the airport service do not canceled. Those altitudes or speed restrictions annotated have any bearing on air traffic control operations. This with (ATC) may be canceled at the discretion of ATC. Explanation of Changes E of C-1 JO 7110.65T 2/11/10 l. 4-5-7. ALTITUDE INFORMATION o. 9-2-10. LAND-BASED AIR DEFENSE IDENTIFICATION ZONE (ADIZ)/AIR TRAFFIC This change formalizes phraseology for the issuance of CONTROL (ATC) SECURITY SERVICES altitude crossing restrictions that are a specific number of miles and direction from a specified fix or waypoint. This change deletes the reference to terminal and replaces m. 4-8-1. APPROACH CLEARANCE Land-Based Air Defense Identification Zone with Washington, D.C., SFRA. This change cancels and This editorial change aligns the phraseology with other incorporates N JO 7110.503, Washington, D.C., Special similar examples. Flight Rules Area (DC SFRA)/Air Traffic Control (ATC) n. 9-2-9. SPECIAL INTEREST SITES Security Services, effective May 11, 2009. The DEN has been added as a required notification entity p. Additional editorial/format changes were made of unusual aircraft activities in the vicinity of special where necessary. Revision bars were not used because of interest sites. the insignificant nature of these changes. E of C-2 2/11/10 JO 7110.65T Table of Contents Chapter 1. General Section 1. Introduction Paragraph Page 1-1-1. PURPOSE OF THIS ORDER . 1-1-1 1-1-2. AUDIENCE. 1-1-1 1-1-3. WHERE TO FIND THIS ORDER. 1-1-1 1-1-4. WHAT THIS ORDER CANCELS. 1-1-1 1-1-5. EXPLANATION OF CHANGES. 1-1-1 1-1-6. SUBMISSION CUTOFF AND EFFECTIVE DATES. 1-1-1 1-1-7. DELIVERY DATES. 1-1-1 1-1-8. RECOMMENDATIONS FOR PROCEDURAL CHANGES. 1-1-1 1-1-9. PROCEDURAL LETTERS OF AGREEMENT. 1-1-2 1-1-10. CONSTRAINTS GOVERNING SUPPLEMENTS AND PROCEDURAL DEVIATIONS . 1-1-2 1-1-11. SAFETY MANAGEMENT SYSTEM (SMS). 1-1-2 1-1-12. REFERENCES TO FAA NON-AIR TRAFFIC ORGANIZATIONS. 1-1-2 1-1-13. DISTRIBUTION. 1-1-2 Section 2. Terms of Reference 1-2-1. WORD MEANINGS . 1-2-1 1-2-2. COURSE DEFINITIONS . 1-2-2 1-2-3. NOTES . 1-2-2 1-2-4. REFERENCES . 1-2-3 1-2-5. ANNOTATIONS . 1-2-3 1-2-6. ABBREVIATIONS . 1-2-3 Chapter 2. General Control Section 1. General 2-1-1. ATC SERVICE . 2-1-1 2-1-2. DUTY PRIORITY . 2-1-1 2-1-3. PROCEDURAL PREFERENCE . 2-1-1 2-1-4. OPERATIONAL PRIORITY . 2-1-2 2-1-5. EXPEDITIOUS COMPLIANCE . 2-1-3 2-1-6. SAFETY ALERT . 2-1-3 2-1-7. INFLIGHT EQUIPMENT MALFUNCTIONS . 2-1-4 2-1-8. MINIMUM FUEL . 2-1-4 2-1-9. REPORTING ESSENTIAL FLIGHT INFORMATION . 2-1-5 2-1-10. NAVAID MALFUNCTIONS . 2-1-5 2-1-11. USE OF MARSA . 2-1-5 2-1-12. MILITARY PROCEDURES . 2-1-6 2-1-13. FORMATION FLIGHTS . 2-1-6 2-1-14. COORDINATE USE OF AIRSPACE . 2-1-7 2-1-15. CONTROL TRANSFER . 2-1-7 2-1-16. SURFACE AREAS . 2-1-7 Table of Contents i JO 7110.65T 2/11/10 Paragraph Page 2-1-17. RADIO COMMUNICATIONS TRANSFER . 2-1-8 2-1-18. OPERATIONAL REQUESTS . 2-1-9 2-1-19. WAKE TURBULENCE . 2-1-9 2-1-20. WAKE TURBULENCE CAUTIONARY ADVISORIES . 2-1-9 2-1-21. TRAFFIC ADVISORIES . 2-1-10 2-1-22. BIRD ACTIVITY INFORMATION . 2-1-11 2-1-23. TRANSFER OF POSITION RESPONSIBILITY . 2-1-11 2-1-24. WHEELS DOWN CHECK . 2-1-11 2-1-25. SUPERVISORY NOTIFICATION . 2-1-11 2-1-26. PILOT DEVIATION NOTIFICATION . 2-1-12 2-1-27. TCAS RESOLUTION ADVISORIES . 2-1-12 2-1-28. RVSM OPERATIONS . 2-1-12 2-1-29. TERRAIN AWARENESS WARNING SYSTEM (TAWS) ALERTS . 2-1-13 Section 2. Flight Plans and Control Information 2-2-1. RECORDING INFORMATION . 2-2-1 2-2-2. FORWARDING INFORMATION . 2-2-1 2-2-3. FORWARDING VFR DATA . 2-2-1 2-2-4. MILITARY DVFR DEPARTURES . 2-2-1 2-2-5. IFR TO VFR FLIGHT PLAN CHANGE . 2-2-1 2-2-6. IFR FLIGHT PROGRESS DATA . 2-2-1 2-2-7. MANUAL INPUT OF COMPUTER‐ASSIGNED BEACON CODES . 2-2-2 2-2-8. ALTRV INFORMATION . 2-2-2 2-2-9. COMPUTER MESSAGE VERIFICATION . 2-2-2 2-2-10. TRANSMIT PROPOSED FLIGHT PLAN . 2-2-3 2-2-11. FORWARDING AMENDED AND UTM DATA . 2-2-3 2-2-12. AIRBORNE MILITARY FLIGHTS . ..
Recommended publications
  • Historical Summary: Radar Bomb Scoring

    Historical Summary: Radar Bomb Scoring

    HISTORICAL SUMMARY RADAR BOMB SCORING 1945 – 1983 Office of History 1st Combat Evaluation Group Barksdale AFB, Louisiana 09 November 1983 RADAR BOMB SCORING HISTORICAL SUMMARY RBS COMES OF AGE During World War II, allied bomber crews soon discovered that radar was an indispensable aid for strategic bombing. The British employed their bomber forces primarily at night. Thus a means of sighting independent of visibility was required. The American forces also required such a system even though they bombed in daylight. The weather in Europe was so consistently bad during the winter months that strategic bombing could only be accomplished with a radar system. The British were the pioneers in developing such systems while the industrial complex of the U.S. refined and improved their initial efforts. When victory in Europe seemed assured, military efforts focused in the Pacific. Here it became clear that training procedures for radar bombing were in their infant stages and severely lacking. T o correct this, staff work began to develop a training system which would improve crew proficiency in radar bombing through better scoring techniques. Under the jurisdiction of the Army Air Force Tactical Center, an experimental station was established in Jacksonville, Florida to test the training system. These tests proved the value of radar bomb scoring as a means of improving bombing training. Soon thereafter, the Second Air Force took actions to establish a radar bomb scoring station at Kansas City, Missouri, and later, a scoring detachment at Fort Worth, Texas. HQ Second Air Force originally had jurisdiction over this operation but as it grew in size and scope, it became clear that a formal organization was needed to control and manage the new training detachment.
  • Fedora 14 User Guide

    Fedora 14 User Guide

    Fedora 14 User Guide Using Fedora 14 for common desktop computing tasks Fedora Documentation Project User Guide Fedora 14 User Guide Using Fedora 14 for common desktop computing tasks Edition 1.0 Author Fedora Documentation Project [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
  • Managing Large and Complex Systems with Omnispective Analysis and Reasoning

    Managing Large and Complex Systems with Omnispective Analysis and Reasoning

    Managing Large and Complex Systems with Omnispective Analysis and Reasoning Srinivas Chemboli Clive Boughton Research School of Computer Science The Australian National University {srinivas.chemboli, clive.boughton}@anu.edu.au Abstract. Development of newer and more sustainable systems requires a thorough understanding of the complex interactions in current systems. Therefore it is necessary to be able to switch between de- tailed knowledge of component systems and an overall appraisal of the entire system. Current efforts to develop ontologies capturing a "complete" and "universal" understanding of entire systems of systems often result in loss of depth and precision of knowledge contained in the participating systems. This fur- ther adds to the uncertainty and intractability in the management of the complex system. In addition, the absence of a single control and execution context makes it difficult to validate the system against desired intent and goals. All of these increase the likelihood of cost, effort and development time overruns in maintaining, enhancing, retiring and replacing systems. In this paper, we propose a novel approach to address these concerns by the application of Omnispective Analysis and Reasoning (OAR), an epistemic framework for managing intellectual concerns. By creating "localized ontologies" for capturing the ’silos’ of knowledge in component systems, we develop artifacts for only those concerns from the participating domains that are identified as relevant. These localized ontologies can unambiguously capture all relevant system artifacts with valuable information about their context of application within the system. With the OAR framework, we can analyze and manage large systems as an aggregation of all these localized ontologies with explicit specification of mutual inter- actions and influence at the concept, model and implementation levels.
  • Indicators for Missing Maintainership in Collaborative Open Source Projects

    Indicators for Missing Maintainership in Collaborative Open Source Projects

    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb

    Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb

    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
  • Software Im Griff

    Software Im Griff

    COMMUNITY-EDITION Frei kopieren und beliebig weiter verteilen ! 01.2010 01.2010 SOFTWARE IM GRIFF IM GRIFF PAKETE PAKETE Nahtlose Integration S. 32, 59 Fremdpakete konvertieren mit Alien, selbst Kompiliertes paketieren mit Checkinstall Paketmanagement leicht gemacht S. 36, 42, 46, 50, 56 Optimale Softwareverwaltung auf dem Desktop, in der Shell und im Browser für OpenSuse, Fedora, Ubuntu, Mandriva und Debian 6 • RAWSTUDIO • 6 • RAWSTUDIO v Vier Top-Distributionen auf DVD Die brandneuen Ausgaben der beliebtesten Linux-Varianten: OpenSuse 11.2, Fedora 12, Ubuntu 9.10, Mandriva 2010.0 S. 6 - 22 Netzwerkprotokoll Bootmanager der Zukunft: IPv6 S. 84 Grub 2 im Detail S. 74 So funktioniert das Internet Neue Features ausreizen, in der nächsten Generation tückische Fallen umgehen Rätselspaß per Instant-Boot-Linux Point-and-Click S. 82 selbst gebaut S. 60, DVD Preisgekröntes Adventure So setzen Sie mit Tiny Core Machinarium mit knackiger Linux unkompliziert ein Grafi k und pfi ffi gen Ideen Schnellstart-System auf GRUB 2 • OPERA 10.10 • INSTANT-BOOT • IP GRUB 2 • OPERA 10.10 INSTANT-BOOT 4 196067 008502 01 www.linux-user.de EDITORIAL Universelle Speed-Bremse Sehr geehrte Leserinnen und Leser, da ist Linux bei USB 3.0 einmal arbeiter eines großen PC-Herstel- Unsinniger Ramsch also – aber in das erste Betriebssystem, das lers, dass Intel wohl erst 2011 das der schönen neuen Windows-7- eine neue Technik von Haus aus Superspeed-USB in seine Chip- Welt wird er sich verkaufen, kann unterstützt [1], und dann gerät sets integriert [2]. Intel demen- doch Microsofts so reichlich ge- die Markteinführung des neuen tiert nicht.
  • Red Hat Enterprise Linux 7 7.8 Release Notes

    Red Hat Enterprise Linux 7 7.8 Release Notes

    Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Last Updated: 2021-03-02 Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
  • US/US Territories Army

    US/US Territories Army

    DCN 3343 Operations & Training Facilities Area Department Owned US/US Territories Army - Active 18,590 Army - Guard 2,503 Army - Reserve 1,819 Navy - Active 10,320 Navy - Reserve 380 Air Force - Active 12,631 Air Force - Guard 2,799 Air Force - Reserve 626 Marine Corps - Active 2,110 Marine Corps - Reserve 12 DLA 235 TMA 117 WHS 22 Other 9,398 US/US Territories Total 61,562 Non-US Army - Active 4,017 Navy - Active 1,681 Air Force - Active 4,123 Marine Corps - Active 644 TMA 17 Other 557 Non-US Total 11,039 Operations & Training Total 72,601 DCN 3343 Maintenance & Production Facilities Area Department Owned US/US Territories Army - Active 11,154 Army - Guard 640 Army - Reserve 584 Navy - Active 4,389 Navy - Reserve 187 Air Force - Active 4,293 Air Force - Guard 1,125 Air Force - Reserve 169 Marine Corps - Active 868 Marine Corps - Reserve 3 DLA 81 TMA 38 Other 3,263 US/US Territories Total 26,794 Non-US Army - Active 1,161 Navy - Active 526 Air Force - Active 773 Marine Corps - Active 205 DoDEA 1 TMA 2 Other 41 Non-US Total 2,709 Maintenance & Production Total 29,503 DCN 3343 Research, Development, Test, and Evaluation Facilities Area Department Owned US/US Territories Army - Active 2,813 Army - Guard 3 Army - Reserve 12 Navy - Active 2,655 Air Force - Active 1,556 Marine Corps - Active 30 TMA 44 Other 1,191 US/US Territories Total 8,304 Non-US Army - Active 133 Navy - Active 35 Air Force - Active 38 TMA 8 Other 27 Non-US Total 241 Research, Development, Test, and Evaluation Total 8,545 DCN 3343 Supply Facilities Area Department Owned
  • Guide to Air Force Historical Literature, 1943 – 1983, 29 August 1983

    Guide to Air Force Historical Literature, 1943 – 1983, 29 August 1983

    Description of document: Guide to Air Force Historical Literature, 1943 – 1983, 29 August 1983 Requested date: 09-April-2008 Released date: 23-July-2008 Posted date: 01-August-2008 Source of document: Department of the Air Force 11 CS/SCSR (MDR) 1000 Air Force Pentagon Washington, DC 20330-1000 Note: Previously released copies of this excellent reference have had some information withheld. This copy is complete. Classified documents described herein are best requested by asking for a Mandatory Declassification Review (MDR) rather than by asking under the Freedom of Information Act (FOIA) The governmentattic.org web site (“the site”) is noncommercial and free to the public. The site and materials made available on the site, such as this file, are for reference only. The governmentattic.org web site and its principals have made every effort to make this information as complete and as accurate as possible, however, there may be mistakes and omissions, both typographical and in content. The governmentattic.org web site and its principals shall have neither liability nor responsibility to any person or entity with respect to any loss or damage caused, or alleged to have been caused, directly or indirectly, by the information provided on the governmentattic.org web site or in this file. DEPARTMENT OF THE AIR FORCE WASHINGTON, DC 23 July 2008 HAF/IMII (MDR) 1000 Air Force Pentagon Washington, DC 20330-1000 Reference your letter dated, April 9, 2008 requesting a Mandatory Declassification Review (MDR) for the "Guide to Air Force Historical Literature, 1943­ 1983, by Jacob Neufeld, Kenneth Schaffel and Anne E.
  • Velocity, Speed with Direction

    Velocity, Speed with Direction

    Velocity Speed with Direction The Professional Career of Gen Jerome F. O’Malley ALOYSIUS G. CASEY AND PATRICK A. CASEY Air University Press Maxwell Air Force Base, Alabama September 2007 Muir S. Fairchild Research Information Center Cataloging Data Casey, Aloysius G. Velocity : speed with direction : the professional career of Gen Jerome F. O’Malley / Aloysius G. Casey and Patrick Casey. p. ; cm. Includes bibliographical references and index. ISBN 978-1-58566-169-5 1. O’Malley, Jerome F. 2. United States. Air Force—Officers—Biography. 3. Generals —United States—Biography. 4. Air pilots, Military—Biography. 5. Vietnam War, 1961– 1975—Aerial operations, American. I. Title. II. Casey, Patrick, 1960– 358.4/0092––dc22 Disclaimer Opinions, conclusions, and recommendations expressed or implied within are solely those of the authors and do not necessarily represent the views of Air University, the United States Air Force, the Department of Defense, or any other US government agency. Cleared for public release: distribution unlimited. Air University Press 131 West Shumacher Avenue Maxwell AFB, AL 36112-5962 http://aupress.maxwell.af.mil ii Contents Chapter Page DISCLAIMER . ii ABOUT THE AUTHORS . v ACKNOWLEDGMENTS . vii INTRODUCTION . ix 1 The Fatal Crash . 1 2 The Hard Coal Region . 5 3 Saint Rose School . 11 4 Saint Rose Basketball . 23 5 West Point . 37 6 Diane Muennink, Silver Wings, and the Air Force Academy . 47 7 The B-47 Bomber and the General’s Aide . 63 8 The Blackbird SR-71 . 93 9 Colonel O’Malley and Combat in Country . 119 10 Combat Operations in North Vietnam . 129 11 SAC Wing Commander .
  • 1 COMBAT EVALUATION GP.Docx

    1 COMBAT EVALUATION GP.Docx

    1st COMBAT EVALUATION GROUP LINEAGE 1st Radar Bomb Scoring Group constituted, 9 Jun 1954 Activated, 10 Aug 1954 Redesignated 1st Combat Evaluation Group, 1 Aug 1961 STATIONS Carswell AFB, TX Barksdale AFB, LA, 24 Jul 1961 ASSIGNMENTS COMMANDERS Col Otis Parks Col Melvin R. Schultz, Col Jacob A. Hutchison, 16 May 1966 HONORS Service Streamers Campaign Streamers Armed Forces Expeditionary Streamers Decorations EMBLEM MOTTO NICKNAME OPERATIONS The group’s mission was to provide the best possible training and comprehensive evaluation of SAC’s aircrews. On 10 August 1945, the 3903rd Radar Bomb Scoring Group, its three squadrons, and all detachments were discontinued. Simultaneously, the 1st Radar Bomb Scoring Group was activated. This new organization absorbed all personnel and equipment of the 3903rd. By March 1956 the Group consisted of 28 detachments. The numbers of missions scored increased as the size of the organization grew. For example, in 1956 the Group recorded 140,919 attacks against sites. Of these some 127,070 were successfully scored. On 1 August 1961, a major organizational change came to fruition when the Department of the Air Force activated the 1st Combat Evaluation Group at Barksdale AFB, Louisiana. With this action the 1st Radar Bomb Scoring Group and the 3908th Strategic Evaluation Group were merged into one organization. This new organization then had the dual mission of providing radar bomb scoring services as well as standardization and evaluation services. With the advent of B-52 bombing in Southeast Asia in 1965, it soon became apparent that a requisite number of suitable offset aiming points were not available.
  • Hilfreiche Tools Im Linux-Alltag

    Hilfreiche Tools Im Linux-Alltag

    Hilfreiche Tools im Linux-Alltag Edgar 'Fast Edi' Hoffmann Community FreieSoftwareOG [email protected] 6. Mai 2014 Ein Dienstprogramm (auch System- oder Hilfsprogramm, englisch utility) ist ein Computerprogramm, das fur¨ den Benutzer beziehungsweise Systemverwalter eines Computers allgemeine, oft systemnahe Aufgaben ausfuhrt.¨ Ublicherweise¨ geh¨ort eine Reihe von Dienstprogrammen zum Lieferumfang eines Betriebssystems, wobei jedes Dienstprogramm meistens auf eine ganz bestimmte Aufgabe spezialisiert ist. Tools/Hilfsprogramme Begriffserkl¨arung 2 / 43 Ublicherweise¨ geh¨ort eine Reihe von Dienstprogrammen zum Lieferumfang eines Betriebssystems, wobei jedes Dienstprogramm meistens auf eine ganz bestimmte Aufgabe spezialisiert ist. Tools/Hilfsprogramme Begriffserkl¨arung Ein Dienstprogramm (auch System- oder Hilfsprogramm, englisch utility) ist ein Computerprogramm, das fur¨ den Benutzer beziehungsweise Systemverwalter eines Computers allgemeine, oft systemnahe Aufgaben ausfuhrt.¨ 2 / 43 Tools/Hilfsprogramme Begriffserkl¨arung Ein Dienstprogramm (auch System- oder Hilfsprogramm, englisch utility) ist ein Computerprogramm, das fur¨ den Benutzer beziehungsweise Systemverwalter eines Computers allgemeine, oft systemnahe Aufgaben ausfuhrt.¨ Ublicherweise¨ geh¨ort eine Reihe von Dienstprogrammen zum Lieferumfang eines Betriebssystems, wobei jedes Dienstprogramm meistens auf eine ganz bestimmte Aufgabe spezialisiert ist. 2 / 43 Hervorheben des Textes Listendarstellung Durch Plugins erweiterbar Synchronisation uber¨ Cloud Auch fur¨ Windows