<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport http://svn.pydro.noaa.gov/2016/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-E350-TJ-16</ns2:number><ns2:name>Southern Chesapeake Bay</ns2:name><ns2:generalLocality>Chesapeake Bay</ns2:generalLocality><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12866</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions>Local constituents have raised concerns over the accuracy of nautical charts in the area, directly affecting their ability to safely navigate. This project will cover approximately 50 square nautical miles. Survey data from this project is intended to supersede all prior survey data in the common area.</ns2:registryInstructions><ns2:sublocality>Willoughby Bank</ns2:sublocality><ns2:stateOrTerritory>Virginia</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>10000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2016</ns2:year><ns2:chiefOfParty>Chris van Westendorp, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2016-03-09</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2016-04-04</ns2:start><ns2:end>2016-08-25</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:soundingEquipment>Singlebeam Echo Sounder </ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>Hydrographic survey H12866 was completed as specified by hydrographic survey project instructions OPR-E350-TJ-16, signed 09 March 2016. This survey extends from Little Creek, VA to Poquoson, VA.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">37.1389222222</ns2:latitude><ns2:longitude hemisphere="W">76.2706416667</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">36.9336027778</ns2:latitude><ns2:longitude hemisphere="W">76.1891027778</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12866 Project Extents</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/Extents.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Survey H12866, Sheet 1 of OPR-E350-TJ-16 extends from Little Creek in the South to Back River in the North, from Thimble Shoal Channel West to the Hampton Roads Bridge Tunnel (Figure 1).

Deviations were made to the original survey limits as assigned. The Chief of Party made the decision to extend the western perimeter of the sheet limits to include Willoughby Bay Channel and the complete extents of the Hampton Roads Bridge Tunnel based on local reports of dangers to navigation, predominantly shoaling (Figure 2). This extension was acquired using a combination of object detection multibeam collected by hydrographic survey launches and singlebeam data collected by an autonomous Z-boat (Figure 3). Two other allowances of sheet limit deviation were made for further extensions: one obstruction on the eastern side of the project area near the entrance to Little Creek that was cut off by sheet limits (Figure 4) and one fish haven along the northernmost edge of the sheet limit (Figure 5). Both areas were fully developed with object detection multibeam data. 

The project limits were not completed in the vicinity of Phoebus Channel near the northern end of the Hampton Roads Bridge Tunnel due to safety concerns (Figure 6) nor in the northwestern section into Back River due to time and schedule constraints (Figure 7). The southeasterly point of Willoughby Bank also has an area that was not covered by survey data. The area is approximately 100m by 200m (Figure 8).  Two areas without data coverage exist along the northern-most limit of the project area (Figures 9 and 10). Five data coverage gaps exist along the eastern sheet limit that are small, and likely the result of early termination of logging data. The most severe of these is located at 37-08-08.835N 076-11-59.597W. The southern edge of the sheet also has some minor data gaps where the side scan sonar imagery does not meet the inshore-most multibeam data (Figure 11). </ns2:discussion><ns2:images><ns2:caption>Active Captain markers for local concerns to safe navigation. Western survey limits were extended to include markers 4, 2, and 5.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/ActiveCaptain.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Data extends from sheet limits. Surface shown is a 1m interpolated surface of both multibeam and singlebeam data for increased visibility.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/ExtensionA.png</ns2:link></ns2:images><ns2:images><ns2:caption>Data extends from sheet limits to cover obstruction.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/extensionB.png</ns2:link></ns2:images><ns2:images><ns2:caption>Data extends from sheet limits to cover fish haven.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/extensionC.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area South of Old Point Comfort where survey coverage does not meet sheet limit nor 12ft curve. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/LackOCov-Hampton.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Incomplete northern section of Sheet H12866. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/LackOCov-BackRiver.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Data gap South of Willoughby Bank. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/CoverageGap1WillBank.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Data gap along northern sheet limit.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/Ngap1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Data gap along northern sheet limit.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/Ngap2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>SSS coverage gaps.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/angledgaps.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>Local constituents have raised concerns over the accuracy of nautical charts in the area, directly affecting their ability to safely navigate. This project will cover approximately 44 square nautical miles. Survey data from this project is intended to supersede all prior survey data in the common area.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>Inshore Limit to 4 meters</ns2:waterDepth><ns2:requiredCoverage>100 meter Set Line Spacing</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Offshore Shoals of depths 1-4 meters</ns2:waterDepth><ns2:requiredCoverage>50 meter Set Line Spacing</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All waters non-contiguous to shore</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Survey H12866 deviated from the coverage requirements in the area adjacent to North of Hampton Roads Channel, South of Thimble Shoal. Coverage in this area was requested by the Chief of Party to be acquired with object detection multibeam. Survey H12866 utilized several different methods of coverage; object detection multibeam in Thimble Shoal Channel and from the channel North to the southern portion of Thimble Shoal, 50m line spaced vertical beam inshore of the 12ft depth curve (Figure 12), and 100% SSS (Figure 13)with concurrent multibeam. Multibeam data was gridded to both 1m and 50cm specifications and vertical beam was gridded to 1m specifications, as opposed to the required 4m grid. There are four occurrences of 200% side scan sonar data acquired to aid in feature disproval, but all were later reacquired with object detection multibeam (Figure 14). The HDCS data, mosaic, and geotiff are included with the submission of this project even though they were not used to prove or disprove feature occurrence. </ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12866 bathymetric coverage.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/BathyCoverage.jpg</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>H12866 100% Side Scan Sonar coverage.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/SSS100Cov.jpg</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>H12866 200% Side Scan Sonar coverage.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/SSS200Cov.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>3101</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>92.19</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>282.28</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>95.38</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>3102</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>621.98</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>616.73</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>33.97</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Z-1</ns2:hullID><ns2:statistics><ns2:MS_SBES>7.08</ns2:MS_SBES><ns2:MS_MBES>0</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0.48</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Z-2</ns2:hullID><ns2:statistics><ns2:MS_SBES>193.64</ns2:MS_SBES><ns2:MS_MBES>0</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>9.98</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>200.72</ns2:MS_SBES><ns2:MS_MBES>714.17</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>899.01</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>139.81</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>7.70</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>0</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>44.74</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2016-04-04</ns2:surveyDates><ns2:surveyDates>2016-04-06</ns2:surveyDates><ns2:surveyDates>2016-04-07</ns2:surveyDates><ns2:surveyDates>2016-04-08</ns2:surveyDates><ns2:surveyDates>2016-04-11</ns2:surveyDates><ns2:surveyDates>2016-04-12</ns2:surveyDates><ns2:surveyDates>2016-04-15</ns2:surveyDates><ns2:surveyDates>2016-04-18</ns2:surveyDates><ns2:surveyDates>2016-04-19</ns2:surveyDates><ns2:surveyDates>2016-04-21</ns2:surveyDates><ns2:surveyDates>2016-04-22</ns2:surveyDates><ns2:surveyDates>2016-04-25</ns2:surveyDates><ns2:surveyDates>2016-04-26</ns2:surveyDates><ns2:surveyDates>2016-04-27</ns2:surveyDates><ns2:surveyDates>2016-04-29</ns2:surveyDates><ns2:surveyDates>2016-05-02</ns2:surveyDates><ns2:surveyDates>2016-05-03</ns2:surveyDates><ns2:surveyDates>2016-05-06</ns2:surveyDates><ns2:surveyDates>2016-05-09</ns2:surveyDates><ns2:surveyDates>2016-05-10</ns2:surveyDates><ns2:surveyDates>2016-05-11</ns2:surveyDates><ns2:surveyDates>2016-05-12</ns2:surveyDates><ns2:surveyDates>2016-05-13</ns2:surveyDates><ns2:surveyDates>2016-05-16</ns2:surveyDates><ns2:surveyDates>2016-05-17</ns2:surveyDates><ns2:surveyDates>2016-05-20</ns2:surveyDates><ns2:surveyDates>2016-05-24</ns2:surveyDates><ns2:surveyDates>2016-05-25</ns2:surveyDates><ns2:surveyDates>2016-05-26</ns2:surveyDates><ns2:surveyDates>2016-05-27</ns2:surveyDates><ns2:surveyDates>2016-05-31</ns2:surveyDates><ns2:surveyDates>2016-06-02</ns2:surveyDates><ns2:surveyDates>2016-06-03</ns2:surveyDates><ns2:surveyDates>2016-06-07</ns2:surveyDates><ns2:surveyDates>2016-06-09</ns2:surveyDates><ns2:surveyDates>2016-06-14</ns2:surveyDates><ns2:surveyDates>2016-06-15</ns2:surveyDates><ns2:surveyDates>2016-06-16</ns2:surveyDates><ns2:surveyDates>2016-06-20</ns2:surveyDates><ns2:surveyDates>2016-06-21</ns2:surveyDates><ns2:surveyDates>2016-06-24</ns2:surveyDates><ns2:surveyDates>2016-07-27</ns2:surveyDates><ns2:surveyDates>2016-07-29</ns2:surveyDates><ns2:surveyDates>2016-08-04</ns2:surveyDates><ns2:surveyDates>2016-08-10</ns2:surveyDates><ns2:surveyDates>2016-08-11</ns2:surveyDates><ns2:surveyDates>2016-08-15</ns2:surveyDates><ns2:surveyDates>2016-08-16</ns2:surveyDates><ns2:surveyDates>2016-08-17</ns2:surveyDates><ns2:surveyDates>2016-08-18</ns2:surveyDates><ns2:surveyDates>2016-08-23</ns2:surveyDates><ns2:surveyDates>2016-08-24</ns2:surveyDates><ns2:surveyDates>2016-08-25</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>HSL 3101</ns2:hullID><ns2:LOA units="feet">31</ns2:LOA><ns2:draft units="feet">5.2</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>HSL 3102</ns2:hullID><ns2:LOA units="feet">31</ns2:LOA><ns2:draft units="feet">5.2</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>Z-1</ns2:hullID><ns2:LOA units="feet">5.5</ns2:LOA><ns2:draft units="feet">1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>Z-2</ns2:hullID><ns2:LOA units="feet">5.5</ns2:LOA><ns2:draft units="feet">1</ns2:draft></ns1:vessel><ns1:discussion>Data was acquired by 3101, 3102, Z1, and Z2. The four platforms collected Reson multibeam echosounder soundings, singlebeam echosounder soundings, multibeam backscatter data, side scan sonar imagery, sound velocity profiles, surface sound speed readings, and position and attitude data.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>7125 SV2</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Klein</ns2:manufacturer><ns2:model>5000 V1</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Odom</ns2:manufacturer><ns2:model>Echotrac CV100</ns2:model><ns2:type>SBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix </ns2:manufacturer><ns2:model>Applanix M/V v4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>Seacat 19+</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>SPS461</ns2:model><ns2:type>Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SV-70</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>The Thomas Jefferson hydrographic survey launches and autonomous survey vessels collected 139.81 linear nautical miles of MBES and VBES crosslines, equating to 7.71% of mainscheme MBES and VBES data. As section 5.2.4.3 of the 2016 HSSD outlines, combined vertical beam and multibeam crossline mileage for mixed echosounder set line spacing surveys must meet the minimum requirement of 8% of mainscheme mileage. Survey H12866 does not meet this specification. Crosslines were compared to mainscheme by differencing a 1m resolution mainscheme surface to a 1m resolution crossline surface in CARIS BASE Editor 4.2. 99.97% of differenced nodes agree within 0.5m. The mean was 0.0m and the standard deviation was 0.1m (Figure 15). The large values of minimum and maximum differences of -3.2m and 2.9m respectively, stem from areas of high relief such as the northern fish haven. The difference surface was filtered to specifically examine the locations of values from -3.2m to -0.49m and 0.49m to 2.9m. No outstanding or systemic errors were noted in the data. </ns2:discussion><ns2:images><ns2:caption>Results of surface differencing between mainscheme and crossline surfaces. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/diffXLs_MS.jpg</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.092</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>3101</ns2:hullID><ns2:measuredCTD units="meters/second">4</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>3102</ns2:hullID><ns2:measuredCTD units="meters/second">4</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Z-1</ns2:hullID><ns2:measuredCTD units="meters/second">4</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Z-2</ns2:hullID><ns2:measuredCTD units="meters/second">4</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty values for survey H12866 were derived using a combination of: real time uncertainties for vessel motion; a priori values for equipment and vessel characteristics; an a priori value for the separation model used to reduce soundings to chart datum; and field assigned values for sound speed uncertainties. The realtime uncertainties for vessel motion include roll, pitch, gyro, navigation, and elevation. The uncertainties in these measurements were recorded as part of the POSPac Real Time Kinematic position solution, as well as the POSPac smartbase IAPPK solution, and were applied to the soundings via an SBET RMS file generated by Applanix POSPac 7.2. Uncertainties for sonar mounting and vessel speed were based on Appendix 4, table 4.9 of the NOAA Field Procedures Manual (ed 2014). These uncertainties were applied to the data via the CARIS HIPS Vessel File. The uncertainty associated with the VDatum separation model was supplied by the Hydrographic Surveys Division’s Operations Branch, and is listed under Zoning (Table 6). Finally, the uncertainty associated with sound speed measurements was based on the frequency and location of CTD casts, in accordance with the guidance set by Appendix 4 of the FPM (ed2014) (Table 7).

Total Propagated Uncertainty was then evaluated to ensure compliance with section 5.1.3 of NOAA's Hydrographic Surveys Specifications and Deliverables. First, the maximum allowable uncertainty for each node was calculated using the equation: -Uncertainty/((0.5^2+((Depth*0.013)^2))^0.5). Second, the ratio between actual uncertainty and maximum allowed uncertainty was found for each node. The resulting 'TVU_QC' layer was filtered using a color map to show any areas where actual uncertainty exceeded the maximum allowed uncertainty. Additionally the Pydro CSAR QA tool was utilized for each surface to be submitted. 

For grid H12866_MB_50cm_MLLW_Final.csar, 99.9% of nodes passed uncertainty standards (Figure 16). 15 nodes out of 222,903,224 exceed allowable TVU tolerances. All nodes out of TVU allowance are confined to an area around the Hampton Roads Bridge Tunnel at 36-59-35.584 N and 076-18-39.893 W (Figure 17). These were reviewed, and the excessive uncertainty appears to be associated mainly with the slopes of 1-2m bedforms in that locale. Refraction error associated with sound velocity profiles may also be a minor contributor. The 50cm gridded surface appears to be unaffected and shows no sign of honoring the outlying nodes.

For grid H12866_MB_1m_MLLW_Final.csar, 99.9% of nodes passed uncertainty standards (Figure 18). 2,663 nodes out of 3,122,257 million exceed allowable TVU tolerances. Most of these nodes are confined to the area south of Old Point Comfort in and along the periphery of Thimble Shoal Channel. These were reviewed, and the excessive uncertainty appears to be associated mainly with refraction error associated with sound velocity profiles. As seen in Figures 19 and 20, sound velocity profile depths for this day did not extend to the deepest bathymetry collected and is at the root of the TVU bust. </ns2:discussion><ns2:images><ns2:caption>H12866_MB_50cm_MLLW_Final Uncertainty Standards statistics utilizing Pydro CSAR QA.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/H12866_MB_50cm_MLLW_FINAL.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area of grid nodes exceeding allowable TVU for H12866_MB_50cm_MLLW.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/50cmSurfTVUexceeds.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>H12866_MB_1m_MLLW_Final Uncertainty Standards statistics utilizing Pydro CSAR QA.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/H12866_MB_1m_MLLW_FINAL.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area of grid nodes exceeding allowable TVU for H12866_MB_1m_MLLW.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/1mSurfTVUexceeds.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Deepest sound velocity profile from HSL 3101 on DN127 (&lt;20m) applied to data with depths greater than 30m. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/1mSurfTVUexceedsSVP.jpg</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>No contemporary junction surveys exist in the area of H12866.</ns2:discussion><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Approximately every 4 hours</ns1:castFrequency><ns1:discussion>CTD casts performed by launches 3101 &amp; 3102 were taken at a maximum of 4 hour intervals; or more frequently in areas where sound speed changed by greater than 2m/sec. If 3101 or 3102 was tending either Z-1 or Z-2, the launch would take a singlebeam specific cast and apply it to the proper ASV's master sound velocity file. Figure 21 shows acquired data colored by sound velocity cast. </ns1:discussion><ns1:images><ns2:caption>H12866 geographic distribution of sound velocity casts from 3101 and 3102.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/H12866_SVP.jpg</ns2:link></ns1:images><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>Refer to section A.4 and B.1.2 of this report for survey equipment and methods used to meet coverage requirements for this project.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Outer Beam Filtering</ns2:title><ns2:discussion>Hydrographic Survey Launch 3101 data exhibited high uncertainty in the outer beams, as data was collected at  maximum swath angle. A filter was created in CARIS 9.1 HIPS to reject all data greater than 65 degrees from nadir for both port and starboard beams in the bulk of the multibeam data collected by 3101. Ultimately, the overall mean uncertainty values for the survey were lowered by a significant amount after filtering was applied. </ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw backscatter was logged as a 7k file and was processed by the field unit. A backscatter project was created for each vessel and will be submitted as a deliverable with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS and SIPS</ns1:name><ns1:version>9.1.2</ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>Fledermaus</ns1:manufacturer><ns1:name>FMGT</ns1:name><ns1:version>7.6.4</ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_4</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12866_MB_50cm_MLLW_FINAL</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.81</ns2:min><ns2:max units="meters">20.00</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12866_MB_1m_MLLW_FINAL</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">17.59</ns2:min><ns2:max units="meters">31.26</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12866_VB_1m_MLLW_FINAL</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.80</ns2:min><ns2:max units="meters">16.58</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12866_SSS_100_1m</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">0</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12866_SSS_200_1m</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">0</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>200% SSS</ns2:purpose></ns1:surface><ns1:discussion>Submitted multibeam grids for survey H12866 exceed the full coverage requirements assigned by the project instructions. Both the 1m and 50cm surfaces meet object detection requirements for density as described in section 5.2.2.2 of the HSSD 2016 (Figures 22 and 23). For further discussion, see section A.4 of this report. </ns1:discussion><ns1:images><ns2:caption>98.7% of H12866_MB_50cm_MLLW_FINAL passes density requirements for object detection multibeam. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/H12866_MB_50cm_MLLW_FINAL.density.png</ns2:link></ns1:images><ns1:images><ns2:caption>99.5% of H12866_MB_1m_MLLW_FINAL passes density requirements for object detection multibeam. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/H12866_MB_1m_MLLW_FINAL.density.png</ns2:link></ns1:images><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:issue><ns2:title>Survey Lines With No Delayed Heave </ns2:title><ns2:discussion>Several lines of multibeam data exist within survey H12866 that have no associated delayed heave. Lines from launch 3101 missing delayed heave are: 118_138_1459, 161_388_1429, 209_301_1734, 209_347_1835, and 228_316_1632. Lines from launch 3102 missing delayed heave are: 145_319_1337, 145_322_1426, 145_320_1408, 145_318_1320, 145_321_1352, 172_224_1823, and 166_401_1405. Hypothetically, there is a correlation between line length and the ability to incorporate delayed heave data into the line information. Message from CARIS:  &quot;WARNING: Delayed heave was selected for the above lines, but no data was found. Only heave has been applied&quot;. The Hydrographer assesses the effect on data collected for which there is no delayed heave applied appears to be negligible.

The autonomous survey vessels used to acquire vertical beam data have no heave sensor, and therefore, no heave data. Positioning correctors applied to verticalbeam data are derived from a Real Time Kinematic solution. </ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Surface Fliers</ns2:title><ns2:discussion>H12866_MB_1m_MLLW_FINAL grid scanned for fliers at 50cm tolerance yielded 18 potential fliers. After review and directed editing, remaining flagged nodes were determined to be valid objects.  

H12866_MB_50cm_MLLW_FINAL grid scanned for fliers at 50cm tolerance yielded 2526 potential fliers. 2475 of these exist within two fish havens expected to have significant relief. 2381 are located within the northernmost fish haven, 76 are located in the southern fish haven. The remaining 69 flagged fliers were reviewed and deemed valid objects.

H12866_VB_1m_MLLW_FINAL grid scanned for fliers at 50cm tolerance yielded 0 potential fliers. 

Several of the initially flagged fliers were particularly difficult to identify as the flier itself could only be observed in the 3-D subset view and not 2-D subset. CARIS HIPS 9.1.2 is unable to resolve some isolated surface areas in 2-D subset and reviewers should be aware of this bug. </ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Kiptopeke</ns2:stationName><ns2:stationID>8632200</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Yorktown</ns2:stationName><ns2:stationID>8637689</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Sewells Point</ns2:stationName><ns2:stationID>8638610</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Chesapeake Bay Bridge Tunnel</ns2:stationName><ns2:stationID>8638863</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>8662200.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>8637689.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>8638610.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>8638863.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>E350TJ2016.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2016-08-30</ns2:dateSubmitted><ns2:dateReceived>2016-09-13</ns2:dateReceived></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-E350-TJ-16_ExtendedSEP</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>WGS84</ns2:horizontalDatum><ns2:projection>18N</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations/><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="true"><ns2:discussion>A RTK base station was installed on top of the Atlantic Hydrographic Branch in Norfolk, VA. For further information, reference the accompanying HVCR with this report. </ns2:discussion><ns2:comments/></ns2:RTK><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>Surveyed soundings were compared to existing charted soundings by two separate methods to ensure agreement in results. The first method differenced surveyed soundings to to an interpolated grid of existing ENC soundings in BASE Editor 4.2. The second method utilized exported ASCII data, both surveyed soundings and ENC soundings, from BASE Editor 4.2 and assessed comparison of surveyed soundings to charted soundings.  The areas of greatest change were then flagged in a feature layer populated with cartographic symbols. The resultant generalized cartographic symbol layer accurately portrayed areas of shoaling and significant change, while the most significant difference points and areas (most likely to be dangers to navigation, or DtoNs) were flagged in a separate layer. The area encompassed within survey H12866 showed relative stability to previously charted data. However, areas of shifting shoals pose dangers throughout, as noted in the Danger to Navigation Reports located in Appendix II and submitted with this report. Both methods of assessing changes to charted bathymetry resulted in a good visual representation of change.

In the area immediately South of Thimble Shoal Light, a shoal has developed with depths ranging up to 9m shoal to charted soundings. It appears a south easterly shift in Thimble Shoal is the primary contributor to this accretion (Figure 24). The United States Army Corps of Engineers, Norfolk District has scheduled dredging this area for early 2017 and will be using the removed material to renourish the beach along bay-side sections of Willoughby Spit (ref Appendix II of this report). 

The easternmost reach of Willoughby Bank has shifted southeast by approximately 140m, taking along with it the shoalest of the charted soundings (Figure 25). This shift resulted in the submission of DtoN Report 1, which can be found in Appendix II of this report. At the time this report was submitted, the effected charts have been updated with the instance of shoaling described in DtoN Report 1. 

Another significant occurrence of shoaling has developed in the vicinity of 36-59-27.525N 076-17-38.990W. A surveyed sounding of 15ft was found in the vicinity of a 22ft charted sounding (Figure 26). This was determined not to be a danger to navigation. 

Other significant areas of shoaling have occurred along the southern portion of the Hampton Roads Bridge Tunnel in the vicinity of Fort Wool. Willoughby Channel, to the West, is known to have dangerous shoaling around 36-58-52.166N 076-18-38.438W (Figure 27). Shoaling was reported in DtoN Report 1 found in Appendix II of this report. A supplementary Aid to Navigation had been placed prior to this survey, and the charted depth curve has been updated to reflect this change, but danger of grounding still exists. At the time this report was submitted, the effected charts have been updated with the instance of shoaling described in DtoN Report 1. 

On the North end of the Hampton Roads Bridge Tunnel and along the shoreline of Old Point Comfort, surveyed depths are shoal to charted soundings on the magnitude of 2-5m (Figure 28). 

In the northern section of the survey, shoals have shown general eastward movement on the magnitude of 75m to 140m from charted positions (Figure 29). Two dangers to navigation were submitted in this area: DtoN Report 3 and DtoN Report 5 (Appendix II). DtoN 3 exists at 57-06-14.186N 076-15-12.590W where a 2ft sounding was surveyed 120m outside of the charted 6ft contour, in between a 19ft and and 18ft charted sounding (Figure 30). DtoN 5 is within the Back River Channel where shoaling is threatening the safe passage of the channel (Figure 31). At the time this report was submitted, the effected charts have been updated with the instances of shoaling described in both DtoN Report 3 and DtoN Report 5.

Both large fish havens within the survey limits have depths shoal to charted authorized minimum depths. Two DtoNs were submitted from surveyed depths within the northern fish haven: DtoN 2 and DtoN 4. DtoN 2 is a pile of debris with a least depth of 8ft; DtoN 4 is a pile of debris with a least depth of 11ft (Figure 32). At the time this report was submitted, the effected charts have been updated with the instances of shoaling described in both DtoN Report 2 and DtoN Report 4. In the southern fish haven, one debris pile exceeds authorized minimum by less than 0.5ft. An uncharted shipwreck with a least depth of 21.59ft exists along the northern border of the fish haven (Figure 33).

As the shoals have shifted, so too have the deeps. In general, as the faces of the shoals have shifted eastward the surveyed depths behind them now read deep to the charted soundings. Two areas found to be deeper than charted are: an area of scour under the Hampton Roads Bridge Tunnel (possibly due to construction work on the tunnel) and an area where sand has been physically removed for beach renourishment 3km East of Buckroe Beach.  

With the exception of the shoaling and other objects noted above, the bathymetry of survey H12866 agrees well with existing charted information. For further analysis of charted and new features, refer to the Final Feature File submitted with this report.</ns2:discussion><ns2:images><ns2:caption>Thimble Shoal has shifted in a southeasterly direction causing a mass of sand to accrete in the vicinity of Thimble Shoal Light. This area will be a material source for a beach renourishment project undertaken by the USACE in early 2017. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/ThimbleShoalShoaling.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Shifting shoal of Willoughby Bank.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/Willoughby.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Shoaling along northern Willoughby Bank and the southern section of the Hampton Roads Bridge Tunnel.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/FtWool.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Shoaling in Willoughby Channel. Dangerous encroachment of sediment into channel is highlighted in red circle . Aid to Navigation was placed before current survey and is on station serving its intended purpose. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/WilloughbyBayChan.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Shoaling noted along the North end of the Hampton Roads Bridge Tunnel and along the southern edge of Old Point Comfort. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/ShoalingOldPtComf.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>General eastward movement of charted shoals in the vicinity of Back River including 2 DtoNs.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/ShiftingShoalsNorth.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Danger to Navigation number 3. Surveyed 2ft sounding 120m East of nearest 5ft contour. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/DtoN3.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Danger to Navigation number 5. Shoaling is encroaching into Back River Channel. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/DtoN5.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Northern fish haven with authorized minimum of 15ft. Current survey found 3 soundings shoal to authorized minimum, 2 of which were reported as DtoNs. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/FishHavenN.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>The southern fish haven has one debris pile with a least depth of 19.69ft. There is also an uncharted ship wreck just beyond the northern boundary of the fish haven with a least depth of 21.59ft. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-E350-TJ-16%20Southern%20Chesapeake%20Bay/H12866/Separates/Descriptive_Report/Report/DR%20Images/FishHavenS.jpg</ns2:link></ns2:images><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12222</ns2:number><ns2:kapp>1</ns2:kapp><ns2:scale>40000</ns2:scale><ns2:edition>55</ns2:edition><ns2:editionDate>2015-02</ns2:editionDate><ns2:LNMDate>2016-11-10</ns2:LNMDate><ns2:NMDate>2016-11-10</ns2:NMDate></ns2:chart><ns2:discussion>NOAA RNC 12222 covers the entire area of survey H12866 at a scale of 1:40000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report. </ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12254</ns2:number><ns2:kapp>1</ns2:kapp><ns2:scale>20000</ns2:scale><ns2:edition>50</ns2:edition><ns2:editionDate>2016-05</ns2:editionDate><ns2:LNMDate>2016-11-12</ns2:LNMDate><ns2:NMDate>2016-11-12</ns2:NMDate></ns2:chart><ns2:discussion>NOAA RNC 12254 covers the southeastern area of survey H12866 at a scale of 1:20000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12245</ns2:number><ns2:kapp>1</ns2:kapp><ns2:scale>20000</ns2:scale><ns2:edition>68</ns2:edition><ns2:editionDate>2013-05</ns2:editionDate><ns2:LNMDate>2016-11-12</ns2:LNMDate><ns2:NMDate>2016-11-12</ns2:NMDate></ns2:chart><ns2:discussion>NOAA RNC 12245 covers the southwestern area of survey H12866 at a scale of 1:20000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US5VA13M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>35</ns2:edition><ns2:updateApplicationDate>2016-09-27</ns2:updateApplicationDate><ns2:issueDate>2016-11-27</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA ENC US5VA13M covers the northern area of survey H12866 from Buckroe Beach to Back River at a scale of 1:40000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5VA15M</ns2:name><ns2:scale>20000</ns2:scale><ns2:edition>45</ns2:edition><ns2:updateApplicationDate>2016-08-11</ns2:updateApplicationDate><ns2:issueDate>2016-08-11</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA ENC US5VA15M covers the southwestern area of survey H12866 at a scale of 1:20000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report. </ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5VA18M</ns2:name><ns2:scale>5000</ns2:scale><ns2:edition>15</ns2:edition><ns2:updateApplicationDate>2016-07-20</ns2:updateApplicationDate><ns2:issueDate>2016-07-20</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA ENC US5VA18M covers a small area of survey H12866 in the vicinity of Little Creek at a scale of 1:5000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5VA20M</ns2:name><ns2:scale>20000</ns2:scale><ns2:edition>14</ns2:edition><ns2:updateApplicationDate>2016-07-20</ns2:updateApplicationDate><ns2:issueDate>2016-07-20</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA ENC US5VA20M covers the southeastern area of survey H12866 at a scale of 1:20000. Any changes to assigned features derived from the ENC can be found in the Final Feature File included with this report. For a general description of bathymetric changes, refer to section D.1 of this report. </ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5VA24M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>25</ns2:edition><ns2:updateApplicationDate>2016-11-07</ns2:updateApplicationDate><ns2:issueDate>2016-11-07</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> Survey H12866 encompassed several obstructions and wrecks with the designation of PA, ED, PD, or Rep. For full details, see the Final Feature File submitted with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> For full details, see the Final Feature File submitted with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>5</ns2:numberSubmitted><ns2:discussion>Danger to Navigation Reports are included in Appendix II of this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>  For full details, see the Final Feature File submitted with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>  For full details, see the Final Feature File submitted with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="None Exist"><ns2:discussion>No bottom samples were required for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Prior survey comparisons exist for this survey, but were not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>All Aids to Navigation within the sheet limits of survey H12866 were found to be on station and serving their intended purpose. </ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion> For full details, see the Final Feature File submitted with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="Investigated"><ns2:discussion> For full details, see the Final Feature File submitted with this report. </ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="Investigated"><ns2:discussion>Present and/or planned construction or dredging exists within the survey limits. The easternmost point of Thimble Shoal will be dredged in early 2017 by the USACE and material used to renourish Willoughby beaches. There is on-going construction and maintenance on the HRBT. </ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="true"><ns2:discussion>The area of Back River that was not completed during this survey should be prioritized for placement in the assignment queue. </ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Chris van Westendorp, CDR/NOAA</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2016-12-12</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Matthew R. Forrest, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approvalDate>2016-12-12</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Allison C Stone</ns2:approverName><ns2:approverTitle>Senior Survey Technician</ns2:approverTitle><ns2:approvalDate>2016-12-12</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>