From:Woods, Bobby L CDR USN COMTHIRDFLT (USA) To:Oden, David Maddux (Dave) CAPT USN COMTHIRDFLT (USA) Cc:Hockran, Paul A CAPT USN (USA); Larson, Amy K CAPT USN COMTHIRDFLT (USA); Clauze, Jeremy Lynn CDR USN COMTHIRDFLT (USA); Hoy, Cara A LCDR USN COMTHIRDFLT (USA); Krigbaum, Dayton A CDR USN SOUTHCOM SC-CC (USA) Subject:(U) CPF DRAFT UAS REPORTING MSG RFI Date:Tuesday, May 21, 2019 1:57:01 PM Attachments:CPF DRAFT UAS REPORTING MESSAGE -14 MAY_1500.docx Classification: UNCLASSIFIED MOC-D, ALCON. BLUF: Sir attached is the CPF draft UAS reporting message for C3F review and comments. I have read subj message and have no issues with the content. CDR Bobby Woods Fleet Security Officer Antiterrorism Deputy Director (N34D) Commander THIRD Fleet Naval Station Point Loma BLDG C60, RM 323 San Diego, CA 92147 NIPR:
[email protected] SIPR:
[email protected] Classification: UNCLASSIFIED P XXXXXXZ MAY 19 FM COMPACFLT PEARL HARBOR HI TO ALPACFLT COMSEVENTHFLT COMTHIRDFLT COMNAVMARIANAS GU COMNECCPAC PEARL HARBOR HI NAVFAC PACIFIC PEARL HARBOR HI COMNAVREG HAWAII PEARL HARBOR HI NMCPAC EAST ASIA DIV PEARL HARBOR HI COMNAVREGCTR SINGAPORE COMSC PAC SAN DIEGO CA COMSC FAR EAST SINGAPORE COMSUBPAC PEARL HARBOR HI INFO CNO WASHINGTON DC HQ USPACOM J3 DIRSSP WASHINGTON DC COMUSFLTFORCOM NORFOLK VA HQ USNORTHCOM COMUSJAPAN YOKOTA AB JA COMNAVFORJAPAN YOKOSUKA JA COMNAVREGJAPAN YOKOSUKA JA COMUSFK SEOUL KOREA COMNAVFORKOREA BUSAN KOR COMNAVREGKOREA SEOUL KOR COMNAVSURFPAC SAN DIEGO CA COMNAVAIRPAC SAN DIEGO CA COMSUBPAC PEARL HARBOR HI COMSC NORFOLK VA COMDT COGARD WASHINGTON DC ONI WASHINGTON DC DIRNAVCRIMINVSERV QUANTICO VA COGARD MSC WASHINGTON DC CNIC WASHINGTON DC COMNAVRESFOR NORFOLK VA COMSPAWARSYSCOM SAN DIEGO CA NAVSURFWARCEN DAHLGREN VA BUPERS MILLINGTON TN NAVINTACT WASHINGTON DC NAVY JAG WASHINGTON DC BUMED FALLS CHURCH VA COMFLTCYBERCOM FT GEORGE G MEADE MD COMOPTEVFOR NORFOLK VA COMNAVSUPSYSCOM MECHANICSBURG PA COMNAVAIRSYSCOM PATUXENT RIVER MD COMNAVFACENGCOM WASHINGTON DC COMNAVSEASYSCOM WASHINGTON DC COMPACFLT PEARL HARBOR HI// UNCLASSIFIED FOUO MSGID/GENADMIN/CPF/-/ MAY// SUBJ/(U//FOUO) CONSOLIDATED PACFLT OPERATIONAL REPORTINGREQUIREMENTS OF UNMANNED AIRCRAFT SYSTEM (UAS) INCIDENTS FOR INSTALLATIONS AND AT-SEA UNITS// REF/A/GENADMIN/COMPACFLT/240100ZJUL18// REF/B/GENADMIN/COMPACFLT/051933ZDEC17// REF/C/GENADMIN/COMUSFLTFORCOM NORFOLK VA/211900ZJUN16// REF/D/GENADMIN/COMPACFLT/XXXXXXZMAY19// REF/E/OPTASK/COMPACFLT/XXXXXXZMAY19// REF/F/DOC/OPNAV/-/04OCT2011// NARR/REF A IS PACFLT OPERATIONAL REPORTING OF UAS INCIDENTS AND FAA NOTIFICATION REQUIREMENTS BY NAVY INSTALLATIONS, FACILITIES, AND UNITS IN THE PACOM AOR. REF B IS COMPACFLT MSG SUBJ COUNTER SMALL AIRCRAFT SYSTEM (C-SUAS) GUIDANCE FOR PACFLT AFLOAT UNITS OPERATING IN OR NEAR FOREIGN PORTS. REF C IS USFF/CPF MSG SUBJ OPERATIONAL REPORTING OF UAS ENCOUNTERED BY NAVY INSTALLATIONS AND FACILITIES. REF D IS COMPACFLT MSG SUBJ PHONE NOTIFICATIONS TO FAA REGARDING UAS ENGAGEMENTS WITHIN THE U.S. REF E IS COMPACFLT OPTASK VISUAL INFORMATION. REF F IS OPNAVINST F3100.6J NAVY SPECIAL INCIDENT REPORTING PROCEDURES.// RMKS/1. (U/FOUO) THIS MESSAGE IS DESIGNED TO CONSOLIDATE UAS REPORTING REQUIREMENTS FOR BOTH INSTALLATIONS AND FACILITIES AND AT-SEA UNITS. REFS A AND B ARE CANCELLED. PACFLT PORTION OF REF C IS RESCINDED.// 2. ( U/FOUO) FEDERAL AVIATION ADMINISTRATION (FAA) NOTIFICATION. PARAGRAPH 2 APPLIES TO BOTH INSTALLATIONS AND FACILITIES AND AT-SEA UNITS OPERATING IN THE UNITED STATES AND TERRITORIES . THE FAA REQUIRES AN IMMEDIATE VOICE NOTIFICATION OF ANY UAS INCIDENT IN THE UNITED STATES AND TERRITORIES THAT INVOLVES THE ENGAGEMENT OF ANY UA WITH INTENT TO DISRUPT OR DISABLE IT, REGARDLESS OF FLIGHT STATUS (I.E. IN FLIGHT, ON GROUND, CAUGHT IN TREE) AND REGARDLESS OF THE COUNTERMEASURE USED. REF D CONTAINS PROCEDURES FOR FAA NOTIFICATIONS.// 3. (U/FOUO) VISUAL INFORMATION (VI) REPORTS. PARAGRAPH 3 APPLIES TO BOTH INPORT AND AT-SEA UNITS. VISUAL SIGHTINGS OF A UAS DOES NOT IN AND OF ITSELF MEET VI REPORTING CRITERIA. UNIT COMMANDING OFFICERS, SHIPS MASTERS, AND MISSION COMMANDERS SHOULD TAKE INTO CONSIDERATION THE ACTIONS OF THE UAS AND MAKE THE DETERMINATION IF THE INTERACTION MAY HAVE NATIONAL LEVEL INTEREST. REF E CONTAINS PROCEDURE FOR VI REPORTS.// 4. (U/FOUO) OPREP-3 REPORTING GUIDANCE FOR SMALL UAS (S-UAS) 4.A. (U/FOUO) INPORT/INSTALLATION AND FACILITIES UAS REPORTING. 4.A.1. (U/FOUO) REPORTING OF UAS INPORT/INSTALLATION AND FACILITIES INCIDENTS WILL FOLLOW REF F OPREP-3 GUIDANCE AND FORMAT FOR VOICE AND MESSAGE TRAFFIC AS AMPLIFIED BELOW. ALL PACFLT COMMANDS, INSTALLATIONS, FACILITIES, OUTLYING ACTIVITIES, AND UNITS ARE DIRECTED TO REPORT ANY CONFIRMED S-UAS ACTIVITY (VALIDATED VIA VISUAL OBSERVATION AND/OR VERIFIED SENSOR DATA) IN THE VICINITY OF THEIR UNIT OR WITHIN THE AIRSPACE OVER OR ADJACENT TO THE HOST INSTALLATION OR FACILITY. IN ORDER TO PREVENT MULTIPLE OPREP-3 REPORTS FOR THE SAME UAS SIGHTING, THE FOLLOWING CRITERIA DETERMINE REPORTING PROCEDURES: 4.A.1.A. UAS OBSERVATIONS IN A NAVY CONTROLLED PORT OR AIRFIELD. SHIPS, SUBMARINES, AND AIRCRAFT SHALL REPORT UAS OBSERVATIONS THAT DO NOT IMPACT THEIR UNIT TO THEIR HOST INSTALLATION IAW INSTALLATION PROCEDURES. 4.A.1.B. UAS INTERACTIONS THAT IMPACT A UNIT IN A NAVY CONTROLLED PORT OR AIRFIELD. IF THE UAS HAZARDS, HARASSES OR OTHERWISE IMPACTS YOUR UNIT, REPORT INCIDENT IAW OPREP-3 PROTOCOL AND THIS MESSAGE. ENSURE TO INFO HOST INSTALLATION. 4.A.2. (U/FOUO) REPORTING GUIDANCE: THE SCENARIOS BELOW ARE GUIDELINES. COMMANDING OFFICERS SHOULD EVALUATE EACH UAS INCIDENT TO DETERMINE IF HIGHER LEVEL REPORTING IS WARRANTED. 4.A.2.A. UAS INCIDENTS REQUIRING REPORTS FALL INTO ONE OF THREE CATEGORIES. (1) OPREP-3 PINNACLE: SHOULD BE SENT AT THE DISCRETION OF THE COMMANDING OFFICER FOR INCIDENTS MEETING PINNACLE THRESHOLD (REF F). (2) OPREP-3 NAVY BLUE: THIS INCLUDES (A) ANY UAS INCIDENT WHERE MEASURES WERE TAKEN, EITHER KINETIC OR NON-KINETIC, TO DISRUPT, DESTROY, OR DISABLE A UAS. (B) ANY UAS INCIDENT WHERE THERE IS A MISSION IMPACT, REGARDLESS OF WHETHER MITIGATION MEASURES WERE TAKEN; (C) ANY UAS INCIDENT THE UNIT, INSTALLATION, OR MISSION COMMANDER DEEMS N ECESSARY TO INFORM THE NMCC; (D) ANY UAS INCIDENT THAT MAY GENERATE SIGNIFICANT PRESS INTEREST OR THE INVOLVEMENT OF LOCAL LAW ENFORCEMENT OR OTHER OUTSIDE-THE-UNIT OR INSTALLATION (3) OPREP-3 NAVY UNIT SITREP: ANY CONFIRMED UAS SIGHTING OR DETECTION OVER OR ADJACENT TO A SHIP, SUBMARINE, AIRCRAFT, UNIT, INSTALLATION, FACILITY OR ASSET, REGARDLESS OF MISSION ACTIVITY AT THE TIME OR SIGHTING. (SEE NAVY CONTROLLED PORT / HOMEPORT- CAVEAT PARA 4.A.1.A ABOVE). 4.A.2.B. (U/FOUO) REPORT FORMAT / INFORMATION REQUIRED: REF F DOES NOT SPECIFICALLY ADDRESS UAS INCIDENTS, OTHER THAN AS DIRECT SURVEILLANCE INCIDENTS. UNTIL A CHANGE TO REF F IS RELEASED, INITIAL MESSAGE REPORTING FOR INPORT/INSTALLATION AND FACILITIES EVENTS (OPREP-3 PINNACLE, NAVY BLUE, OR NAVY UNIT SITREP) SHALL INCLUDE THE FOLLOWING: LINE 1 - DTG OF INCIDENT LINE 2 - LOCATION OF INCIDENT: MILITARY GRID REFERENCE SYSTEM (MGRS) AND DESCRIPTION (I.E., VICINITY POST EXCHANGE, AIRFIELD, HOUSING AREA, ETC.) LINE 3 - SUAS OBSERVATION SOURCE: IF REPORTED BY SUBORDINATE UNIT, INCLUDE THE UNITS INFORMATION. IF GENERATED FROM OPERATIONAL OR INTELLIGENCE REPORTING, LIST REPORT SERIAL NUMBER OR OTHER IDENTIFYING INFORMATION (SERIAL NUMBER, DATE-TIME GROUP OF MESSAGE, LINE 4 - NUMBER OF SUAS: IF ONE OBSERVATION WITH MULTIPLE DEVICES, DESIGNATE EACH DEVICE AS UAS-1, UAS-2, UAS-3, ETC, THROUGH THE REMAINDER OF THE REPORT. ENSURE MULTIPLE UAS OBSERVED ARE DISTINCT AND NOT THE SAME UAS BEING REPORTED BY MULTIPLE OBSERVERS. LINE 5 - SUAS TYPE (DESCRIPTION): TYPE: (ROTOR - QUADCOPTER, FIXED WING, OTHER, UNKNOWN). DESCRIPTION: (COLOR(S), MARKINGS [DECALS, STRIPES, LINES], LIGHTS [NUMBER, COLOR, POSITION ON DEVICE], PAYLOAD [CAMERA, SENSOR, OTHER DEVICES]). LINE 6 - SUAS FLIGHT DETAILS (DESCRIPTION): DIRECTION (FROM AND TOWARD), SPEED (SLOW, MODERATE, FAST, VERY FAST), ALTITUDE (APPROXIMATE IN METERS), BEHAVIOR (TRAVELING, HOVERING, FOLLOWING). LINE 7 - PERCEIVED SUAS INTENT: SURVEILLANCE, RECREATIONAL, NUISANCE, PROFESSIONAL CIVILIAN USE, PHYSICAL ATTACK, OTHER (DESCRIBE), UNKNOWN. LINE 8 - IDENTIFICATION OF SUAS OPERATORS: NUMBER, LOCATION, (DESCRIPTION) OR UNKNOWN. LINE 9 - C-UAS SYSTEMS ON-HAND: YES (NUMBER / TYPE) OR NONE. LINE 10 - C-UAS SYSTEMS EMPLOYED IAW ROE: YES (NUMBER, TYPE), NO (EXPLAIN WHY NOT USED). LINE 10A - C-UAS EMPLOYMENT RESULTS: UAS FLIGHT DISRUPTED (DESCRIBE, IE. DEVICE DEPARTED AREA), UAS FLIGHT TERMINATED (DESCRIBE, I.E. DEVICE LANDED, CRASHED), NO OBSERVED EFFECT ON DEVICE, UNKNOWN. LINE 10B - SUAS RECOVERY / DISPOSITION: COMPLETE IF UAS FLIGHT TERMINATED. YES: (INCLUDE DEVICE CONDITION, CURRENT LOCATION, WHO HAS CUSTODY, ETC.) OR NO: (EXPLAIN WHY NOT RECOVERED AND LOCATION OF FLIGHT TERMINATION). LINE 11 - TOTAL ELAPSED TIME OF INCIDENT: LIST THE TIME IN MINUTES OF THE OVERALL INCIDENT (I.E. 1 HOUR AND 5 MINUTES = 65). LINE 12 - EXTERNAL COORDINATION / NOTIFICATIONS CONDUCTED: ORGANIZATIONS OR UNITS WITH DTG (IE. FAA, HOST NATION THROUGH COUNTRY TEAM, USFK OR USFJ, LAW ENFORCEMENT [CID, NCIS, AFOSI, LINE 13 - REPORTING ORGANIZATION POC: NAME/RANK, POSITION, ORGANIZATION, PHONE NUMBER, EMAIL ADDRESS (SIPR AND NIPR). 4.A.2.C. (U) STORYBOARD REQUIREMENTS: A STORYBOARD IS A GRAPHIC REPRESENTATION OF AN INCIDENT AND IS GENERALLY DEPICTED ON A POWERPOINT SLIDE. WITHIN 12 HOURS AFTER THE COMPLETION OF AN INCIDENT, UNITS SHALL PROVIDE A STORYBOARD TO PROVIDE GREATER DETAIL ON THE EVENT. A SINGLE SLIDE IS TYPICAL, BUT MULTIPLE SLIDES MAY BE USED FOR EXTENDED OR COMPLEX EVENTS. AT A MINIMUM, STORYBOARDS SHALL INCLUDE A MAP BACKGROUND, AN INSET MAP SHOWING THE AREA COVERED BY THE MAIN MAP, A NORTH ARROW, A NUMBERED DISTANCE SCALE, WEATHER, AND A UNIT CO OR WARFARE COMMANDER'S COMMENT CHARACTERIZING THE BEHAVIOR OF THE FOREIGN ENTITIES AND LEVEL OF PERCEIVED THREAT. IN ADDITION, STORYBOARDS SHOULD INCLUDE DESCRIPTIVE IMAGES OF THE ACTIVITY IF SPACE IS AVAILABLE. MULTIPLE REPORTABLE EVENTS (I.E. DURING A FREEDOM OF NAVIGATION OPERATION) CAN BE REPRESENTED BY A SINGLE MISSION STORYBOARD. STORYBOARDS SHOULD BE CLASSIFIED IF THEY REVEAL PPRS, TACTICS, OR INDICATIONS AND WARNING. VERSIONS UP TO TS/SCI CAN BE PRODUCED IF USEFUL FOR CONVEYING ALL CONTEXT. PROPERLY MARK THE CLASSIFICATION OF EACH IMAGE AND TEXT ANNOTATION IN THE 4.A.2.C.1. (U) THERE IS NO NEED TO DUPLICATE WORK, AND A STORYBOARD PRODUCED AS A VI PRODUCT (PARA 3 ABOVE) WILL MEET THE OPREP-3 STORYBOARD REQUIREMENT. DO NOT NEED TO CREATE A STORYBOARD FOR VI AND A SEPARATE STORYBOARD TO ACCOMPANY THE OPREP-3 REPORT. 4.A.2.C.2. (U) PACFLT MOC MAY NEED ADDITIONAL INFORMATION AFTER RECEIPT OF THE STORYBOARD, THEREFORE THE REPORTING COMMAND MUST BE PREPARED TO PROVIDE A DETAILED ASSESSMENT OF THE INCIDENT. 4.B. (U/FOUO) AT-SEA UAS REPORTING (INTERNATIONAL WATERS) 4.B. 1. (U/FOUO) REPORTING OF UAS INCIDENTS AT SEA WILL FOLLOW REF F OPREP-3 GUIDANCE AND FORMAT FOR VOICE AND MESSAGE TRAFFIC AS AMPLIFIED BELOW. ALL PACFLT UNITS AT-SEA ARE DIRECTED TO REPORT ANY CONFIRMED S-UAS ACTIVITY IN THE VICINITY OF THEIR UNIT. 4.B.2. (U/FOUO) REPORTING GUIDANCE: THE SCENARIOS BELOW ARE GUIDELINES. COMMANDING OFFICERS SHOULD EVALUATE EACH S-UAS INCIDENT TO DETERMINE IF HIGHER LEVEL REPORTING IS WARRANTED. 4.B.2.A. UAS INCIDENTS REQUIRING REPORTS FALL INTO ONE OF THREE CATEGORIES. (1) OPREP-3 PINNACLE: SHOULD BE SENT AT THE DISCRETION OF THE COMMANDING OFFICER FOR INCIDENTS MEETING PINNACLE THRESHOLD (REF F). (2) OPREP-3 NAVY BLUE: THIS INCLUDES (A) ANY UAS INCIDENT WHERE MEASURES WERE TAKEN, EITHER KINETIC OR NON-KINETIC, TO DIRSRUPT, DESTROY, OR DISABLE A UAS, (B)ANY UAS INCIDENT WHERE THERE IS A MISSION IMPACT, REGARDLESS OF WHETHER MITIGATION MEASURES WERE TAKEN; (C) ANY UAS INCIDENT THE UNIT DEEMS NECESSARY TO INFORM THE NMCC; (D) ANY UAS INCIDENT THAT MAY GENERATE SIGNIFICANT PRESS INTEREST. (3) OPREP-3 NAVY UNIT SITREP: ANY CONFIRMED UAS SIGHTING OR DETECTION NEAR AN AFLOAT UNIT. 4.B.2.B. (U) REPORT FORMAT / INFORMATION REQUIRED: SAME AS 4.A.2.B. 4.B.2.C. (U) STORYBOARD REQUIREMENTS: SAME AS 4.A.2.C. 4.B.3. (U) SPY DATA TAPES: SEND SPY DATA TAPES TO NAVAL SURFACE WARFARE CENTER DETACHMENT DAHLGREN (NSWCDD) AS SOON AS OPERATIONALLY FEASIBLE FOR ANALYSIS. DIRLAUTH WITH NSWCDD IS AUTHORIZED. EMAIL: DLGR_NSWC_REACHBACK(AT)NAVY.SMIL.MIL. 4.B.3.A. ADDRESS OUTER PACKAGING TO: NAVAL SURFACE WARFARE CENTER DAHLGREN PROCESSING CENTER 6146 TISDALE RD, SUITE 237 DAHLGREN, VA 22448-5158 4.B.3.B. ADDRESS INNER PACKAGING TO: NAVAL SURFACE WARFARE CENTER DAHLGREN ATTN: ROB WARD, NSWCDD 6146 TISDALE RD, SUITE 237 5. (U/FOUO) SECURITY/CLASSIFICATION: COMPILING THE UNCLASSIFIED INFORMATION IN A REPORT MAY MAKE THE MESSAGE CLASSIFIED. FOR THOSE WITH UNCLASS XMIT CAPABILITY ONLY - IF ANY INFORMATION REQUIRED IN NOTIFICATION AND REPORTING PROCEDURES EXCEEDS THE CLASSIFICATION ALLOWED BY TRANSMISSION MODE, STATE INFORMATION EXCEEDS THE CLASSIFICATION OF THE TRANSMISSION MODE - ON FILE WITH THE REQUESTOR NEXT TO THE APPROPRIATE PARAGRAPH, AND FOLLOW UP AS APPLICABLE TO SUPPORT REQUIRED INFORMATION SHARING.// 6. (U) POINTS OF CONTACT. 6.A. CPF BATTLE WATCH CAPTAIN (BWC): NIPR EMAIL: CPF.CATBWC(AT)NAVY.MIL SIPR EMAIL: CPF.CATBWC.FCT 6.B. CPF C-UAS AT/FP POC (LCDR R. SMOOT): NIPR EMAIL: REGGIE.SMOOT(AT)NAVY.MIL SIPR EMAIL: REGGIE.SMOOT 6.C. CPF SUAS REPORTING GUIDANCE POC (MR. F. BRUMMER): NIPR EMAIL: FRED.BRUMMER(AT)NAVY.MIL SIPR EMAIL: FRED.BRUMMER(AT)NAVY.SMIL.MIL (DSN) 315-471-9816 From:C3F_BWC To:Alexander, John D VADM USN COMTHIRDFLT (USA) Cc:C3F All Front Office; C3F_Surgeon; C3F JAG; C3F FOPS; C3F COPS; C3F All ACOS & SA & Deputies; CPF.CATBWC; Cerezo, Joseph L LCDR USN COMTHIRDFLT (USA); Clauze, Jeremy Lynn CDR USN COMTHIRDFLT (USA); Follett, Sarah L CDR USN (USA); Hockran, Paul A CAPT USN (USA); Oden, David Maddux (Dave) CAPT USN COMTHIRDFLT (USA); Plank, Mckenzie S LCDR USN (USA) Subject:(U) GBG UAS interaction **Corrected Email** Date:Thursday, July 25, 2019 6:32:54 AM Classification: UNCLASSIFIED//FOUO BLUF: GBG Operating 10NM S of San Clemente Island when 4 UAV's were identified proceeding inbound and orbiting around USS Gabrielle Giffords, while conducting MQ8 Flight OPS. GBG Landed, refueled, and re-launched MQ-8 to investigate small UAS and try to determine small UAS point of origin. Three small boats were in the vicinity, two unidentified and one Identified as Pez Ezpada. GBG queried Pre Ezpada with no response. Awaiting release of Very Respectfully, LCDR Edward Cruzmatos C3F Battle Watch Captain
[email protected] [email protected] Classification: UNCLASSIFIED//FOUO From:Smith, Jacob W ISC DDG60 To:Hutchins, Abigail A CDR USN COMTHIRDFLT (USA); C3F_BWC; C3F COPS; C3F_ABWC;
[email protected]; Fowler, David E CAPT USN COMNAVSURFPAC SAN (USA);
[email protected]; Heames, Jeffrey L CAPT USN COMDESROM 23 (USA);
[email protected]; Yates, Kendra M LT USN (USA); Yates, Kendra M LT USN (USA); CPF.CATBWC; cpf.catpao Cc:"
[email protected]"; "
[email protected]"; "
[email protected]"; "
[email protected]"; "
[email protected]"; "
[email protected]"; ATO; CO; Combat Systems Khaki; OPS; PTO; TAO; XO Subject:(U) USS PAUL HAMILTON/VIR/CHINA/MV BASS STRAIT/150511ZJUL19 Date:Monday, July 15, 2019 4:31:25 AM Attachments:150511ZJUL19.MV BASS STRAIT.PHM.001.UNCLAS.jpg 150511ZJUL19.MV BASS STRAIT.PHM.QUICKLOOK STORYBOARD.UNCLAS.pptx 150511ZJUL19.MV BASS STRAIT.PHM.001.UNCLAS.mp4 150511ZJUL19.MV BASS STRAIT.PHM.001.UNCLAS.jpg 150511ZJUL19.MV BASS STRAIT.PHM.003.UNCLAS.JPG.jpg Classification: UNCLASSIFIED 1. (U) Attached is VI from USS PAUL HAMILTON. Amplifying information: Interaction with HONG KONG flagged Merchant Vessel BASS STRAIT likely operating UAVs. 2. (U) Units involved: USS PAUL HAMILTON (DDG-60); M/V BASS STRAIT. 3. (U) Files attached: STORYBOARD; 2X JPEG; 1X VIDEO. 150511ZJUL19.MV BASS STRAIT.PHM.001.UNCLAS.JPG 150511ZJUL19.MV BASS STRAIT.PHM.002.UNCLAS.JPG 150511ZJUL19.MV BASS STRAIT.PHM.003.UNCLAS.JPG 150511ZJUL19.MV BASS STRAIT.PHM.001.UNCLAS.MP4 150511ZJUL19.MV BASS STRAIT.PHM.QUICKLOOK STORYBOARD.UNCLAS.PPTX 4. (U) USS PAUL HAMILTON is in international waters approximately 70 NM E of San Clemente Island, CA. 5. (U) LATITUDE/LONGITUDE: 3256160N 11949875W. 6. (U) DESCRIPTION OF THE EVENT: 0511Z: SNOOPIE Team called away for VOI MV BASS STRAIT approximately 6200YDS from PHM. MV BASS STRAIT's course was 058T at 06KTS. 0545Z: UAV was 048T from PHM 0554Z: 3x UAV were 266T astern from PHM 0556Z: UAV was 355T from PHM 0600Z: UAV was 082T from PHM 0602Z: UAV was near PHM's STBD bow 0624Z: UAV was PORT QTR moving to Starboard 0631Z: UAV was 280T 2NM astern from PHM 0639Z: 3x drones on near STBD QTR 0646Z: All UAVs headed toward TR 0650Z: UAV off STBD QTR 0652Z: UAV off PORT QTR 0659Z: 2x UAVs at 124T, ALT 1400ft; 4x UAVs off PORT QTR CO declared VI event complete and secured SNOOPIE Team Nothing further to report. No impact to PHM's mission. Very respectfully, ISC(IW/SW/EXW) Jacob W. Smith USS Paul Hamilton (DDG-60) Ship's IDIS Classification: UNCLASSIFIED USS PAUL HAMILTONThe Courage to Prevail UNCLASSIFIED UNCLASSIFIED BLUF: (U)USS PAUL HAMILTON (PHM) conducting routine operations in the SOCAL OPAREA observed MV BASS STRAIT likely using UAVs to conduct surveillance on US Naval Forces while transiting to scheduled port of call, Long Beach, CA. 15 JUL19: MV BASS STRAIT (U) MV BASS STRAIT Via PHM SNOOPIE TEAM MV BASS STRAIT PHMLocation: Timeline of Events 1. 0511Z: SNOOPIE Team called away for VOI MV BASS STRAIT approximately 6200YDS from PHM. MV BASS STRAITs course was 058T 2.0545Z: UAV was 048T from PHM 3.0554Z: 3x UAV were 266T astern 4.0556Z: UAV was 355T from PHM 5.0600Z: UAV was 082T from PHM 6.0602Z: UAV was near PHMs STBD 7.0624Z: UAV was PORT QTR moving to Starboard 8.0631Z: UAV was 280T 2NM astern 9.0639Z: 3x drones on near STBD QTR 10.0646Z: All UAVs headed toward TR 11.0650Z: UAV off STBD QTR 12.0652Z: UAV off PORT QTR 4x UAVs off PORT QTR 14.0900Z: CO declared VI event complete and secured SNOOPIE Distance Scale Video/Photos capture point(s) Current as of 150900ZJUL19 From:Eben R. Moore, Eben R. LT IWO (DDG 1000) To:C3F_BWC; C3F_ABWC; C3F COPS; Hutchins, Abigail A CDR COMTHIRDFLT; "
[email protected]"; "
[email protected]"; Fowler, David E CAPT C