<?xml version="1.0" encoding="utf-8"?>
<dr:descriptiveReport xmlns:dr="http://svn.pydro.noaa.gov/2024/01/DescriptiveReport" xmlns:hsd="http://svn.pydro.noaa.gov/2024/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2024/01/DescriptiveReport http://svn.pydro.noaa.gov/2024/01/DR.xsd">
    <dr:metadata>
        <dr:projectMetadata>
            <hsd:number>OPR-S327-KR-24</hsd:number>
            <hsd:name>Kotzebue, AK</hsd:name>
            <hsd:generalLocality>Kotzebue, AK</hsd:generalLocality>
            <hsd:fieldUnit>Terrasond</hsd:fieldUnit>
        </dr:projectMetadata>
        <dr:registryMetadata>
            <hsd:registryNumber>H13923</hsd:registryNumber>
            <hsd:sheetID>12</hsd:sheetID>
            <hsd:registryInstructions>na</hsd:registryInstructions>
            <hsd:sublocality>16 NM Northwest of Espenberg</hsd:sublocality>
            <hsd:stateOrTerritory>Alaska</hsd:stateOrTerritory>
            <hsd:country>United States</hsd:country>
            <hsd:scale>40000</hsd:scale>
        </dr:registryMetadata>
        <dr:surveyMetadata>
            <hsd:year>2024</hsd:year>
            <hsd:chiefOfParty>Andrew Orthmann</hsd:chiefOfParty>
            <hsd:projectType>Navigable Area</hsd:projectType>
            <hsd:PIDate>2024-05-01</hsd:PIDate>
            <hsd:datesOfSurvey>
                <hsd:start>2024-07-05</hsd:start>
                <hsd:end>2024-10-18</hsd:end>
            </hsd:datesOfSurvey>
            <hsd:equipmentTypes>
                <hsd:soundingEquipment>Multibeam Echo Sounder</hsd:soundingEquipment>
                <hsd:imageryEquipment>Multibeam Echo Sounder Backscatter</hsd:imageryEquipment>
            </hsd:equipmentTypes>
            <hsd:acquisition>
                <hsd:units>meters</hsd:units>
            </hsd:acquisition>
            <hsd:timeZone>UTC</hsd:timeZone>
            <hsd:verifier>Pacific Hydrographic Branch</hsd:verifier>
            <hsd:titlesheetRemarks>
                <hsd:fieldRemarks xsi:nil="true" />
                <hsd:branchRemarks>Any revisions to the Descriptive Report (DR) applied during office processing are shown in red italic text. The DR is maintained as a field unit product, therefore all information and recommendations within this report are considered preliminary unless otherwise noted. The final disposition of survey data is represented in the NOAA nautical chart products. All pertinent records for this survey are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via https://www.ncei.noaa.gov/. 

Products created during office processing were generated in WGS84 UTM 3N, MLLW. All references to other horizontal or vertical datums in this report are applicable to the processed hydrographic data provided by the field unit.</hsd:branchRemarks>
            </hsd:titlesheetRemarks>
        </dr:surveyMetadata>
        <dr:dataLicense>
            <hsd:classification>CC0-1.0 (NOAA Contractors)</hsd:classification>
            <hsd:spdx>
                <hsd:licenseIdentifier>CC0-1.0</hsd:licenseIdentifier>
                <hsd:licenseDeed>https://creativecommons.org/publicdomain/zero/1.0/</hsd:licenseDeed>
                <hsd:legalCode>https://creativecommons.org/publicdomain/zero/1.0/legalcode</hsd:legalCode>
            </hsd:spdx>
            <hsd:description>These data were produced under contract with NOAA and any potential copyright was assigned to NOAA. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0).</hsd:description>
        </dr:dataLicense>
        <dr:assignment>Contractor</dr:assignment>
    </dr:metadata>
    <dr:areaSurveyed>
        <dr:areaDescription>
            <hsd:discussion>The survey area is located in Kotzebue Sound, Alaska.

Kotzebue Sound is located in northwestern Alaska. The Arctic region is unnavigable for most of the year due to sea ice, with open water from approximately July through October. At the time of this survey, most of the area was poorly charted, with some areas uncharted altogether.

The remote area is off the road system, and the bulk of supplies (including fuel) necessary for local communities are transported here by barge during the short ice-free season. Nearby communities are relatively small, consisting primarily of Shishmaref, Kivalina, Deering, and Kotzebue. Members of these communities commonly engage in various subsistence activities throughout Kotzebue Sound, usually traveling by skiff.

Kotzebue is the largest community, with a population of 2,979 (2023). Limited services, including daily jet service to Anchorage, are available here. However, only shallow-draft vessels can navigate directly to Kotzebue due to a shoal of approximately 2 meters depth about 9 NM west of town, which necessitated relatively long transits to Nome—at least a 60-hour round trip—for most rotations and resupplies on this project.

The Port of Red Dog is located on the north side of Kotzebue Sound. The Port serves as the terminal for Red Dog Mine, one of the largest zinc and lead mining operations in the world. Ore is mined year-round and stored at the Port for transport out during the limited ice-free season. Shallow-draft vessels lighter the ore from the Red Dog dock to deep-draft bulk ore carriers, which typically wait at least 3 NM offshore.

On-site field work for project OPR-S327-KR-24 was carried out from July through October 2024. The overall project consisted of thirteen individual surveys. Final processing and reporting occurred from October 2024 through January 2025. Work was completed in accordance with the Hydrographic Survey Project Instructions (dated May 1, 2024), the accompanying Scope of Work, and the NOAA Hydrographic Surveys Specifications and Deliverables (HSSD, 2022 edition).</hsd:discussion>
            <hsd:limits>
                <hsd:northWest>
                    <hsd:latitude hemisphere="N">66.94709455555557</hsd:latitude>
                    <hsd:longitude hemisphere="W">164.94248055555556</hsd:longitude>
                </hsd:northWest>
                <hsd:southEast>
                    <hsd:latitude hemisphere="N">66.68029691666668</hsd:latitude>
                    <hsd:longitude hemisphere="W">163.99383044444443</hsd:longitude>
                </hsd:southEast>
            </hsd:limits>
            <hsd:images>
                <hsd:caption>Figure showing the survey extents.</hsd:caption>
                <hsd:link>SupportFiles\H13923_Survey_Extents.png</hsd:link>
            </hsd:images>
            <hsd:comments />
        </dr:areaDescription>
        <dr:surveyLimits>
            <hsd:results deviation="false">
                <hsd:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</hsd:discussion>
            </hsd:results>
            <hsd:comments />
        </dr:surveyLimits>
        <dr:surveyPurpose>
            <hsd:topic>
                <hsd:discussion>The purpose of this survey is described as follows in the Project Instructions:

This project will provide modern bathymetric data within Kotzebue Sound, Alaska. Kotzebue acts as the service and transportation center for all villages in the northwest region of Alaska, as well as the transfer point between ocean and inland shipping. Portions of Kotzebue Sound were last surveyed between 2011 and 2015, however a majority of the area has not been surveyed to modern standards.

The area experiences significant vessel traffic, particularly near the approaches to Kotzebue and Deering. The survey will focus on collecting data in the highly trafficked corridors, as well as for vessel lightering areas identified by the Western Alaska Tanker Lightering Best Practices Committee. These areas are used for ship-to-ship transfers of oil products, including fuel, which is of key importance to local residents.

Conducting a modern bathymetric survey in this area will address Seabed 2030 data gaps, identify hazards and changes to the seafloor, provide critical data for updating National Ocean Service (NOS) nautical charting products, and improve maritime safety. Survey data from this project is intended to supersede all prior survey data in the common area.</hsd:discussion>
            </hsd:topic>
            <hsd:comments />
        </dr:surveyPurpose>
        <dr:surveyQuality>
            <hsd:adequacy>The entire survey is adequate to supersede previous data.</hsd:adequacy>
            <hsd:discussion xsi:nil="true" />
            <hsd:comments />
        </dr:surveyQuality>
        <dr:surveyCoverage>
            <hsd:coverageRequirement>
                <hsd:waterDepth>All waters in survey area</hsd:waterDepth>
                <hsd:requiredCoverage>Complete a minimum of 12,896 LNM. Unlogged transit mileage, system calibration mileage, and data which do not meet HSSD specifications shall not count towards the completion of the LNM requirement. Notify the COR/Project Manager upon nearing completion of LNM requirement. The final area shall be squared off and ensure the full investigation of any features within the surveyed extent.</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:coverageRequirement>
                <hsd:waterDepth>All waters in survey area</hsd:waterDepth>
                <hsd:requiredCoverage>Set Line Spacing MBES (Refer to HSSD Section 5.2.2.4 Option A)</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:coverageRequirement>
                <hsd:waterDepth>Sheet H13923</hsd:waterDepth>
                <hsd:requiredCoverage>Sounding lines shall be acquired with spacing adequate to collect data at an interval of at least 480 meters</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:results deviation="true">
                <hsd:discussion>Coverage requirements were met. Additional clarification on specific requirements are provided below.

LNM requirements: A minimum of 12,896 LNM was required project-wide. 12,932 LNM were actually acquired. The excess was collected to compensate for incidental data collection such as crossline mileage that exceeded requirements, data acquired during run-ins or run-outs (including in shallow water while scouting depths between lines), and excess overlap (if any). LNM quantities do not include transit or calibration data, or data that doesn't meet HSSD requirements.

Expansion area: More area was completed for this survey sheet than originally planned. After it became evident that some of the project-wide 12,896 LNM requirement would remain after completing all originally assigned areas, the NOAA COR was consulted and permission was granted to expand this survey to the NE and expend remaining project LNM there. Approximately 65 SQNM of additional seafloor was surveyed and added to the H13923 dataset. This area was surveyed to the same standards as the original area. The affected area is shown in the figure below. Applicable emails are included with the survey correspondence.</hsd:discussion>
                <hsd:images>
                    <hsd:caption>Figure showing the originally assigned survey area and the approximate extents of the 65 SQNM "expansion" of this sheet.</hsd:caption>
                    <hsd:link>SupportFiles\Expansion_Area_Overview.png</hsd:link>
                </hsd:images>
            </hsd:results>
            <hsd:comments />
        </dr:surveyCoverage>
        <dr:coverageGraphic>
            <hsd:coverageGraphicImage>
                <hsd:images>
                    <hsd:caption>Figure showing coverage achieved on this survey.</hsd:caption>
                    <hsd:link>SupportFiles\H13923_Survey_Coverage.png</hsd:link>
                </hsd:images>
            </hsd:coverageGraphicImage>
        </dr:coverageGraphic>
        <dr:surveyStatistics>
            <hsd:LNM>
                <hsd:vesselLNM>
                    <hsd:vessel>
                        <hsd:hullID>Poseidon</hsd:hullID>
                        <hsd:statistics>
                            <hsd:MS_SBES>0.0</hsd:MS_SBES>
                            <hsd:MS_MBES>546.27</hsd:MS_MBES>
                            <hsd:MS_lidar>0.0</hsd:MS_lidar>
                            <hsd:MS_SSS>0.0</hsd:MS_SSS>
                            <hsd:MS_SBES_MBES>0.0</hsd:MS_SBES_MBES>
                            <hsd:MS_MBES_SSS>0.0</hsd:MS_MBES_SSS>
                            <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                            <hsd:XL_MBES_SBES>60.74</hsd:XL_MBES_SBES>
                            <hsd:XL_lidar>0.0</hsd:XL_lidar>
                        </hsd:statistics>
                    </hsd:vessel>
                    <hsd:vessel>
                        <hsd:hullID>ASV-LR1</hsd:hullID>
                        <hsd:statistics>
                            <hsd:MS_SBES>0.0</hsd:MS_SBES>
                            <hsd:MS_MBES>243.43</hsd:MS_MBES>
                            <hsd:MS_lidar>0.0</hsd:MS_lidar>
                            <hsd:MS_SSS>0.0</hsd:MS_SSS>
                            <hsd:MS_SBES_MBES>0.0</hsd:MS_SBES_MBES>
                            <hsd:MS_MBES_SSS>0.0</hsd:MS_MBES_SSS>
                            <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                            <hsd:XL_MBES_SBES>17.12</hsd:XL_MBES_SBES>
                            <hsd:XL_lidar>0.0</hsd:XL_lidar>
                        </hsd:statistics>
                    </hsd:vessel>
                </hsd:vesselLNM>
                <hsd:totalLNM>
                    <hsd:MS_SBES>0.0</hsd:MS_SBES>
                    <hsd:MS_MBES>789.7</hsd:MS_MBES>
                    <hsd:MS_lidar>0.0</hsd:MS_lidar>
                    <hsd:MS_SSS>0.0</hsd:MS_SSS>
                    <hsd:MS_SBES_MBES>0.0</hsd:MS_SBES_MBES>
                    <hsd:MS_MBES_SSS>0.0</hsd:MS_MBES_SSS>
                    <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                    <hsd:XL_MBES_SBES>77.86</hsd:XL_MBES_SBES>
                    <hsd:XL_lidar>0.0</hsd:XL_lidar>
                    <hsd:percentXLLNM>9.86</hsd:percentXLLNM>
                </hsd:totalLNM>
            </hsd:LNM>
            <hsd:totalSurveyStats>
                <hsd:bottomSamples>10</hsd:bottomSamples>
                <hsd:maritimeBoundaryPoints>0</hsd:maritimeBoundaryPoints>
                <hsd:DP>0</hsd:DP>
                <hsd:diveOps>0</hsd:diveOps>
                <hsd:SNM>199.3</hsd:SNM>
            </hsd:totalSurveyStats>
            <hsd:surveyDates>2024-07-05</hsd:surveyDates>
            <hsd:surveyDates>2024-07-06</hsd:surveyDates>
            <hsd:surveyDates>2024-07-07</hsd:surveyDates>
            <hsd:surveyDates>2024-07-08</hsd:surveyDates>
            <hsd:surveyDates>2024-07-11</hsd:surveyDates>
            <hsd:surveyDates>2024-10-14</hsd:surveyDates>
            <hsd:surveyDates>2024-10-15</hsd:surveyDates>
            <hsd:surveyDates>2024-10-16</hsd:surveyDates>
            <hsd:surveyDates>2024-10-17</hsd:surveyDates>
            <hsd:surveyDates>2024-10-18</hsd:surveyDates>
            <hsd:discussion>This area was the second lowest priority area in the overall survey area (sheet 12 of 13). However, it was the first to receive survey operations. This was because upon arrival in the region in late June, sea ice still heavily affected the entire project area. After an almost one week wait for ice to clear, H13923 was the first to become safely navigable, with survey starting here on July 5th. Ice conditions were monitored in the higher priority sheets to the north and east, and operations subsequently moved on to those areas as soon as conditions allowed. Emails relating to this issue are included with the survey correspondence.

Operations returned to this sheet near the end of the project for bottom samples, infills, remaining crosslines, and to survey the "expansion" area described previously in this report.</hsd:discussion>
            <hsd:comments />
        </dr:surveyStatistics>
    </dr:areaSurveyed>
    <dr:dataAcquisitionAndProcessing>
        <dr:equipmentAndVessels>
            <dr: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.</dr:discussion>
            <dr:vessels>
                <dr:vessel>
                    <hsd:hullID>Poseidon</hsd:hullID>
                    <hsd:LOA units="meters">41.0</hsd:LOA>
                    <hsd:draft units="meters">2.6</hsd:draft>
                </dr:vessel>
                <dr:vessel>
                    <hsd:hullID>ASV-LR1</hsd:hullID>
                    <hsd:LOA units="meters">7.6</hsd:LOA>
                    <hsd:draft units="meters">1.0</hsd:draft>
                </dr:vessel>
                <dr:images>
                    <hsd:caption>The R/V Poseidon.</hsd:caption>
                    <hsd:link>SupportFiles\Poseidon.png</hsd:link>
                </dr:images>
                <dr:images>
                    <hsd:caption>The ASV-LR1.</hsd:caption>
                    <hsd:link>SupportFiles\ASV-LR1_2024.png</hsd:link>
                </dr:images>
                <dr:discussion>The R/V Poseidon (Poseidon) is a 41 m steel-hull vessel owned and operated by Support Vessels of Alaska. The Poseidon was operated 24/7, acquiring multibeam data and providing housing and facilities for on-site data processing. The vessel was also used to collect bottom samples, conduct sound speed casts, and deploy/recover the ASV-LR1 launch.

The ASV-LR1 (LR1) is a 7.6 m aluminum-hull Autonomous Surface Vessel (ASV). The vessel was configured to be "optionally crewed", enabling it to operate with or without a crew as operations required. When uncrewed it collected multibeam data in close proximity to the Poseidon, normally running parallel lines within 2 NM.</dr:discussion>
                <dr:comments />
            </dr:vessels>
            <dr:equipment>
                <dr:majorSystem>
                    <hsd:type>MBES</hsd:type>
                    <hsd:manufacturer>Teledyne RESON</hsd:manufacturer>
                    <hsd:model>SeaBat T50-R</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>MBES Backscatter</hsd:type>
                    <hsd:manufacturer>Teledyne RESON</hsd:manufacturer>
                    <hsd:model>SeaBat T50-R</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Positioning and Attitude System</hsd:type>
                    <hsd:manufacturer>Applanix</hsd:manufacturer>
                    <hsd:model>POS MV WaveMaster</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Positioning and Attitude System</hsd:type>
                    <hsd:manufacturer>Applanix</hsd:manufacturer>
                    <hsd:model>POS MV OceanMaster</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Sound Speed System</hsd:type>
                    <hsd:manufacturer>Valeport</hsd:manufacturer>
                    <hsd:model>SWiFT SVP</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Sound Speed System</hsd:type>
                    <hsd:manufacturer>AML Oceanographic</hsd:manufacturer>
                    <hsd:model>MicroX SV</hsd:model>
                </dr:majorSystem>
                <dr:discussion>The survey vessels were configured for MBES data collection with nearly identical survey equipment and software.

The Poseidon and LR1 utilized Teledyne Reson Seabat T50-R MBES systems, with surface sound speed measurements provided by AML Oceanographic Micro-X sensors. Both vessels used Applanix POSMVs with submersible IP-68 rated IMUs for attitude and position measurements. QPS QINSy software, running on Microsoft Windows 10-based PCs, was used for multibeam data logging and vessel navigation. Sound speed profiles were collected using a Valeport SWiFT sensor, which was deployed while underway using a C-MAX Vigo winch on the Poseidon, or taken by hand from the LR1 when it was operating with a survey crew.</dr:discussion>
                <dr:comments />
            </dr:equipment>
            <dr:comments />
        </dr:equipmentAndVessels>
        <dr:qualityControl>
            <dr:crosslines>
                <hsd:topic>
                    <hsd:discussion>The percentage of crossline to mainscheme miles is 9.86%.

Effort was made to ensure crosslines (XLs) had good temporal and geographic distribution, were angled to enable nadir-to-nadir comparisons, and that the required minimum percent of mainscheme LNM was achieved.

Crosslines were conducted with all vessels to ensure there was ample overlap for inter-vessel comparisons, with each vessel crossing the other's mainscheme lines. Crosslines were often collected while transiting across the survey area to reach a different survey priority such as bottom sample locations or infills, leading to crosslines that were diagonal to the direction of mainscheme lines.

The crossline analysis was conducted using CARIS HIPS “Line QC Report” process. Each crossline (with all associated file segments) was selected and run separately through the process, which calculated the depth difference between each accepted crossline sounding and a "QC" BASE (CUBE-type) surface’s depth layer created from the mainscheme data. The QC surface was created with the same parameters and resolution used for the final surface, with the important distinction that the QC surface did not include crosslines so as to not bias the results. Differences in depth were grouped by beam number and statistics were computed, including the percentage of soundings with differences from the QC surface falling within IHO Order 1a.

When at least 95% of the sounding differences exceed IHO Order 1a, the crossline was considered to “pass,” but when less than 95% of the soundings compare within IHO Order 1, the crossline was considered to “fail.” A 5% (or less) failure rate was considered acceptable since this approach compares soundings to a surface (instead of a surface to a surface), allowing for the possibility that noisy crossline soundings that don't adversely affect the final surface could be counted as a QC failure in this process.

Lines selected as crosslines and their percentage (%) of soundings passing IHO Order 1a, sorted from highest passing to lowest, are listed below. Note that lines used as crosslines have their "Line Class" attribute set to "Check" within the CARIS HIPS projects provided with the survey deliverables. In addition to lines run specifically as crosslines, these can also include lines run as junction comparisons.

1667-JD292-Poseidon-L2NS13440 -- 100.0% pass
2088-JD291-LR1-L2XL1000 -- 100.0% pass
1668-JD292-Poseidon-L1XL1003 -- 100.0% pass
0133-JD193-Poseidon-L1XL1000 -- 100.0% pass
2089-JD291-LR1-L1XL1003 -- 100.0% pass
0135-JD193-Poseidon-L1XL1001 -- 100.0% pass
1619-JD289-Poseidon-L1XL1002 -- 100.0% pass
1563-JD288-Poseidon-L2NS00000 -- 100.0% pass
1620-JD289-Poseidon-L1NEB -- 100.0% pass
1622-JD289-Poseidon-L1NEB -- 100.0% pass

Results: Agreement between them mainscheme surface and crossline soundings is excellent. At least 95% of all crossline soundings compare to the mainscheme surface within IHO Order 1a for all crosslines. Refer to Separate II: Digital Data for the detailed Crossline QC reports.</hsd:discussion>
                </hsd:topic>
                <hsd:comments />
            </dr:crosslines>
            <dr:uncertainty>
                <hsd:values>
                    <hsd:tideUncertainty>
                        <hsd:tideMethod>ERS via ERTDM</hsd:tideMethod>
                        <hsd:measured units="meters">0.14</hsd:measured>
                        <hsd:zoning units="meters">0.0</hsd:zoning>
                    </hsd:tideUncertainty>
                    <hsd:soundSpeedUncertainty>
                        <hsd:hullID>Poseidon</hsd:hullID>
                        <hsd:measuredCTD units="meters/second">0</hsd:measuredCTD>
                        <hsd:measuredMVP units="meters/second">3.1</hsd:measuredMVP>
                        <hsd:measuredXBT units="meters/second">0</hsd:measuredXBT>
                        <hsd:surface units="meters/second">0.025</hsd:surface>
                    </hsd:soundSpeedUncertainty>
                    <hsd:soundSpeedUncertainty>
                        <hsd:hullID>ASV-LR1</hsd:hullID>
                        <hsd:measuredCTD units="meters/second">0</hsd:measuredCTD>
                        <hsd:measuredMVP units="meters/second">3.1</hsd:measuredMVP>
                        <hsd:measuredXBT units="meters/second">0</hsd:measuredXBT>
                        <hsd:surface units="meters/second">0.025</hsd:surface>
                    </hsd:soundSpeedUncertainty>
                </hsd:values>
                <hsd:discussion>The uncertainty layer of the final surface was examined in CARIS HIPS software, as well as analyzed in Pydro QC Tools V3.10.20 Grid QA v6.

The computed uncertainty of the final grid cells range from 0.358 to 0.781 m. Greater than 99.5% of grid cells have TVU that fall within the allowable range by depth. The largest values are located in the outer beam data on deeper offshore lines, especially during periods with increased vessel motion from rough sea conditions. Areas with the relatively few grid cells with elevated uncertainty were examined and determined to have to final depth values within allowable TVU. All grid cells meet specifications.</hsd:discussion>
                <hsd:comments />
            </dr:uncertainty>
            <dr:junctions>
                <hsd:results performed="true">
                    <hsd:discussion>During field operations, effort was made to ensure sufficient overlap was achieved between this survey and any overlapping surveys for junction analysis. This included extending survey lines into overlapping sheets, and often running lines along junction boundaries.

The "Gridded Surface Comparison V24.6" utility within Pydro was used to compare survey junctions. The utility differences the surfaces from the two surveys and generates statistics that include the percentage of grid cells that compare to within allowable TVU for the depth. 4 m resolution surfaces were used for all sheets completed under this project.

Prior surveys, where applicable, were downloaded from NOAA NCEI in BAG format. The resolution available in NCEI for each BAG surface varied by sheet and is noted below.</hsd:discussion>
                    <hsd:junction>
                        <hsd:survey>
                            <hsd:registryNumber>H12830</hsd:registryNumber>
                            <hsd:scale>40000</hsd:scale>
                            <hsd:year>2015</hsd:year>
                            <hsd:fieldUnit>NOAA Ship Rainier</hsd:fieldUnit>
                            <hsd:relativeLocation>S</hsd:relativeLocation>
                        </hsd:survey>
                        <hsd:discussion>For this survey, a variable resolution (VR) BAG surface was available from NOAA NCEI and used for the comparison with the final surface from this survey.

Agreement between the two surveys is excellent. The mean difference is 0.06 m (with this survey deeper) with a standard deviation of 0.09 m. 100% of grid cells agree within allowable TVU by depth.</hsd:discussion>
                        <hsd:comments />
                    </hsd:junction>
                    <hsd:junction>
                        <hsd:survey>
                            <hsd:registryNumber>H12829</hsd:registryNumber>
                            <hsd:scale>40000</hsd:scale>
                            <hsd:year>2015</hsd:year>
                            <hsd:fieldUnit>NOAA Ship Rainier</hsd:fieldUnit>
                            <hsd:relativeLocation>SE</hsd:relativeLocation>
                        </hsd:survey>
                        <hsd:discussion>For this survey, a variable resolution (VR) BAG surface was available from NOAA NCEI and used for the comparison with the final surface from this survey.

Agreement between the two surveys is excellent. The mean difference is 0.03 m (with this survey shoaler) with a standard deviation of 0.08 m. 100% of grid cells agree within allowable TVU by depth.
</hsd:discussion>
                        <hsd:comments />
                    </hsd:junction>
                    <hsd:junction>
                        <hsd:survey>
                            <hsd:registryNumber>H13914</hsd:registryNumber>
                            <hsd:scale>40000</hsd:scale>
                            <hsd:year>2024</hsd:year>
                            <hsd:fieldUnit>TerraSond</hsd:fieldUnit>
                            <hsd:relativeLocation>E</hsd:relativeLocation>
                        </hsd:survey>
                        <hsd:discussion>These two surveys were completed under the same project. Significant overlap was achieved along their boundary.

Agreement is excellent. The mean difference is 0.07 m (with this survey shoaler) with a standard deviation of 0.09 m. 100% of grid cells agree within allowable TVU by depth.</hsd:discussion>
                        <hsd:comments />
                    </hsd:junction>
                    <hsd:junction>
                        <hsd:survey>
                            <hsd:registryNumber>H13915</hsd:registryNumber>
                            <hsd:scale>20000</hsd:scale>
                            <hsd:year>2024</hsd:year>
                            <hsd:fieldUnit>TerraSond</hsd:fieldUnit>
                            <hsd:relativeLocation>NE</hsd:relativeLocation>
                        </hsd:survey>
                        <hsd:discussion>These two surveys were completed under the same project. There is a small amount of overlap at the NE corner of this survey.

Agreement is excellent. The mean difference is 0.01 m (with this survey shoaler) with a standard deviation of 0.04 m. 100% of grid cells agree within allowable TVU by depth.</hsd:discussion>
                        <hsd:comments />
                    </hsd:junction>
                    <hsd:junction>
                        <hsd:survey>
                            <hsd:registryNumber>H13919</hsd:registryNumber>
                            <hsd:scale>20000</hsd:scale>
                            <hsd:year>2024</hsd:year>
                            <hsd:fieldUnit>TerraSond</hsd:fieldUnit>
                            <hsd:relativeLocation>NE</hsd:relativeLocation>
                        </hsd:survey>
                        <hsd:discussion>These two surveys were completed under the same project. Significant overlap was achieved along their boundary.

Agreement is excellent. The mean difference is 0.02 m (with this survey deeper) with a standard deviation of 0.06 m. 100% of grid cells agree within allowable TVU by depth.</hsd:discussion>
                        <hsd:comments />
                    </hsd:junction>
                    <hsd:images>
                        <hsd:caption>Figure showing survey junctions.</hsd:caption>
                        <hsd:link>SupportFiles\H13923_Survey_Junctions.png</hsd:link>
                    </hsd:images>
                </hsd:results>
                <hsd:comments />
            </dr:junctions>
            <dr:sonarQCChecks>
                <hsd:results deviation="false">
                    <hsd:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:sonarQCChecks>
            <dr:equipmentEffectiveness>
                <hsd:results deviation="true">
                    <hsd:issue>
                        <hsd:title>Poseidon Roll Misalignment</hsd:title>
                        <hsd:discussion>An across-track misalignment, or roll bias, is evident periodically in Poseidon data, adversely affecting outer beam soundings. The exact cause is unknown but is likely attributable to shifts in the POSMV lever arm from movement of the hydraulic MBES arm on the Poseidon. The issue was not observed on the LR1, which also used a hydraulic MBES arm but of significantly less length.

Affected lines were identified by difference surface methodology, wherein a surface made from all soundings was differenced from a TIN surface created using only near-nadir data. Lines that exhibited differences from the TIN approaching or exceeding allowable TVU received additional outer beam filters that rejected the erroneous data. Refer to the DAPR for additional detail on this process.

Following these corrections the negative effect on final surfaces, where this occurs, is generally less than 0.20 m and is within allowable TVU.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                </hsd:results>
                <hsd:comments />
            </dr:equipmentEffectiveness>
            <dr:factorsAffectingSoundings>
                <hsd:results deviation="true">
                    <hsd:issue>
                        <hsd:title>Sound Speed Error</hsd:title>
                        <hsd:discussion>Sound speed error, which is normally characterized by a general upward or downward across-track cupping of sounding data that increases in magnitude towards the outer beams, is evident sporadically in the dataset.

Profiles were taken frequently, usually not exceeding two hours, and whenever changing areas, but some residual error remains. In processing, beam filters were applied to reject outer beams greater than 65 degrees from nadir on all lines in order to reject soundings most subject to sound speed error. The dataset was also systematically examined and additional filters were applied to individual lines where outer beam error appeared to approach or exceed specifications, removing the erroneous data.

The effect on the final surfaces is relatively minor, normally less than 0.20 m where it occurs. Final data is within specifications.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                </hsd:results>
                <hsd:comments />
            </dr:factorsAffectingSoundings>
            <dr:soundSpeedMethods>
                <dr:castFrequency>2 hours</dr:castFrequency>
                <dr:discussion>Sound speed profiles or "casts" were acquired aboard the Poseidon while underway with a C-MAX Vigo profiling winch, utilizing a Valeport SWiFT sound speed profiler. These profiles were used to correct all Poseidon sounding data, as well as all LR1 sounding data for periods when the LR1 was operating uncrewed. This was possible because when uncrewed the LR1 worked in close vicinity to the Poseidon, usually within 2 NM.

However, when operating in crewed mode, casts were also collected abord the LR1. In this case a Valeport SWiFT sound speed profiler was manually lowered to the seafloor. Note that LR1 casts conducted for crewed operations were placed within their own SVP file for CARIS HIPS processing and used only for correcting LR1 crewed data. This was done so that LR1 crewed casts would not be used to correct Poseidon data, and vice versa, since the LR1--when crewed--often operated at significant distance away from the Poseidon. These profiles have "LR1" in the SVP filename in CARIS HIPS. Lines applicable to this SVP file are listed later in this report.

Surface sound speed at the sonar head on the Poseidon (and LR1 when crewed) was monitored continuously and a new cast was collected when the surface speed varied from the previous profile's speed at the same depth by greater than 2 m/s, leading to a cast interval of approximately 2 hours.

Casts were taken as deep as possible. On survey lines with significant differences in depth, the deeper portion of the line was normally favored to ensure that changes across the full water column were measured. The cast data was used to correct the sounding data using the "nearest in distance within time" (set to 2 hours) within CARIS HIPS. Exceptions, if any, are noted later in this report.</dr:discussion>
                <dr:comments />
            </dr:soundSpeedMethods>
            <dr:coverageEquipmentAndMethods>
                <hsd:results deviation="false">
                    <hsd:discussion>All equipment and survey methods were used as detailed in the DAPR.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:coverageEquipmentAndMethods>
            <dr:additionalQualityControl>
                <hsd:comments />
            </dr:additionalQualityControl>
        </dr:qualityControl>
        <dr:echoSoundingCorrections>
            <dr:corrections>
                <hsd:results deviation="true">
                    <hsd:discussion>Crewed LR1 Lines using LR1 SVP file:

The following lines were completed while the LR1 vessel was crewed and conducting its own SVP casts. These utilized the "_LR1" SVP file included with the survey deliverables.

JD291: All lines with prefix 2088 and 2089
</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:corrections>
            <dr:calibrations>
                <hsd:results deviation="false">
                    <hsd:discussion>All sounding systems were calibrated as detailed in the DAPR.</hsd:discussion>
                    <hsd:calibration xsi:nil="true" />
                </hsd:results>
                <hsd:comments />
            </dr:calibrations>
            <dr:additionalIssues>
                <hsd:comments />
            </dr:additionalIssues>
        </dr:echoSoundingCorrections>
        <dr:backscatter>
            <hsd:results acquired="true">
                <hsd:discussion>All equipment and survey methods were used as detailed in the DAPR.</hsd:discussion>
            </hsd:results>
            <hsd:comments />
        </dr:backscatter>
        <dr:dataProcessing>
            <dr:drSoftware>
                <dr:featureObjectCatalog>NOAA Profile Version 2024</dr:featureObjectCatalog>
                <dr:discussion>The most current version of NOAA's Extended Attribute Files available at the start of survey operations was utilized for this project.</dr:discussion>
                <dr:comments />
            </dr:drSoftware>
            <dr:surfaces>
                <dr:surface>
                    <hsd:surfaceName>H13923_MB_4m_MLLW_Final</hsd:surfaceName>
                    <hsd:surfaceType>CARIS Raster Surface (CUBE)</hsd:surfaceType>
                    <hsd:resolution units="meters">4</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min units="meters">18.752</hsd:min>
                        <hsd:max units="meters">25.807</hsd:max>
                    </hsd:depthRange>
                    <hsd:surfaceParameter>NOAA_4m</hsd:surfaceParameter>
                    <hsd:purpose>MBES Set Line Spacing</hsd:purpose>
                </dr:surface>
                <dr:surface>
                    <hsd:surfaceName>H13923_MBAB_2m_400kHz_1of1</hsd:surfaceName>
                    <hsd:surfaceType>MB Backscatter Mosaic</hsd:surfaceType>
                    <hsd:resolution units="meters">2</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min units="meters">18.752</hsd:min>
                        <hsd:max units="meters">25.807</hsd:max>
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>MBES Set Line Spacing</hsd:purpose>
                </dr:surface>
                <dr:discussion>The final depth information for this survey was submitted as a 4 m resolution CARIS BASE surface (CSAR format), computed with the CUBE algorithm, which best represents the seafloor at the time of the 2024 survey. The surface was created from fully processed data with all final corrections applied.

The surface was created using NOAA CUBE parameters and resolutions in conformance with the 2022 HSSD. The surface was finalized with a 0 to 80 m depth limit, "Uncertainty" selected as the final uncertainty source, and designated soundings applied (if present). Horizontal projection was selected as WGS84 / UTM zone 3N.

A non-finalized version of the CSAR surface is also included with the survey deliverables for reference. This does not have the "_Final" designation in the filename.

The Multibeam Acoustic Backscatter (MBAB) surface(s), produced with QPS Fledermaus Geocoder Toolbox (FMGT), is also provided. All vessels ran their sonars at 400 kHz, therefore their MBAB data was combined in a single 400 kHz mosaic.</dr:discussion>
                <dr:comments />
            </dr:surfaces>
            <dr:additionalDataProcessing>
                <hsd:comments />
            </dr:additionalDataProcessing>
        </dr:dataProcessing>
    </dr:dataAcquisitionAndProcessing>
    <dr:verticalAndHorizontalControl>
        <dr:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</dr:discussion>
        <dr:verticalControl>
            <hsd:verticalDatum>Mean Lower Low Water</hsd:verticalDatum>
            <hsd:tideStations />
            <hsd:standard_or_ERZT xsi:nil="true" used="false" />
            <hsd:VDATUM_or_constantSep used="true">
                <hsd:methodsUsed>ERS via ERTDM</hsd:methodsUsed>
                <hsd:ellipsoidToChartDatumSepFile>
                    <hsd:fileName>OPR-S327-KR-24_AK_ERTDM_2023_WGS84(G2139)-MLLW.csar</hsd:fileName>
                </hsd:ellipsoidToChartDatumSepFile>
                <hsd:discussion>All soundings were reduced to MLLW using the ERTDM WGS84 to MLLW separation model grid file provided by NOAA using ERS methodology. The uncertainty stated for the model in the Project Instructions was 0.14 m.

Note all altitudes are relative to the WGS84 datum, therefore the WGS84 to MLLW ERTDM model was utilized to reduce soundings to MLLW.</hsd:discussion>
                <hsd:comments />
            </hsd:VDATUM_or_constantSep>
            <hsd:comments />
        </dr:verticalControl>
        <dr:horizontalControl>
            <hsd:horizontalDatum>World Geodetic System (WGS) 1984</hsd:horizontalDatum>
            <hsd:projection>Projected UTM 3</hsd:projection>
            <hsd:PPK used="true">
                <hsd:methodsUsed>RTX</hsd:methodsUsed>
                <hsd:baseStations />
                <hsd:discussion>Post-processing of all navigation data for final positions was done in Applanix POSPac MMS (v9.1) software. Trimble PP-RTX was used as the primary processing methodology within POSPac. Exceptions (if any) were noted previously.</hsd:discussion>
                <hsd:comments />
            </hsd:PPK>
            <hsd:PPP xsi:nil="true" used="false" />
            <hsd:RTK used="true">
                <hsd:discussion>Real-time positions were primarily RTK. The POSMVs on each vessel were configured to receive Trimble CenterPoint RTX corrections using NTRIP protocol over the internet via Starlink Maritime receivers.

This allowed the POSMVs to operate in RTK mode, assisting with real-time positioning in the field. Real-time positioning sources in the raw MBES records are therefore normally RTX.

However, all real-time positions were replaced in post-processing, as described previously.</hsd:discussion>
                <hsd:comments />
            </hsd:RTK>
            <hsd:DGPS xsi:nil="true" used="false" />
            <hsd:WAAS used="true">
                <hsd:discussion>The Wide Area Augmentation System (WAAS) was used for real-time horizontal control during data acquisition only if issues with reception of CenterPoint RTX corrections were experienced. These are usually noted in the Survey Line Logs, included with the survey deliverables.</hsd:discussion>
                <hsd:comments />
            </hsd:WAAS>
            <hsd:comments />
        </dr:horizontalControl>
        <dr:additionalIssues>
            <hsd:issue>
                <hsd:title>HSSD Section 2.2 (NAD83)</hsd:title>
                <hsd:discussion>A waiver to HSSD Section 2.2 was was granted for this project. All products are submitted with horizontal positions as WGS84 instead of NAD83(2011). This was done to provide a consistent dataset from raw data, which was acquired in WGS84, through final processed data. See project correspondence for the waiver.</hsd:discussion>
                <hsd:comments />
            </hsd:issue>
            <hsd:comments />
        </dr:additionalIssues>
    </dr:verticalAndHorizontalControl>
    <dr:resultsAndRecommendations>
        <dr:chartComparison>
            <dr:methods>
                <hsd:topic>
                    <hsd:discussion>An overview of this survey overlaid on the largest scale chart(s) covering the survey area is shown below.</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>This survey overlaid on affected large scale ENCs. Soundings from this survey are blue. All soundings in meters.</hsd:caption>
                        <hsd:link>SupportFiles\H13923_Sds_on_Charts.png</hsd:link>
                    </hsd:images>
                </hsd:topic>
                <hsd:comments />
            </dr:methods>
            <dr:charts>
                <hsd:ENC>
                    <hsd:name>US4AK6YP</hsd:name>
                    <hsd:scale>80000</hsd:scale>
                    <hsd:edition>2</hsd:edition>
                    <hsd:updateApplicationDate>2024-09-17</hsd:updateApplicationDate>
                    <hsd:issueDate>2024-09-17</hsd:issueDate>
                </hsd:ENC>
                <hsd:ENC>
                    <hsd:name>US4AK6YQ</hsd:name>
                    <hsd:scale>80000</hsd:scale>
                    <hsd:edition>1</hsd:edition>
                    <hsd:updateApplicationDate>2021-03-04</hsd:updateApplicationDate>
                    <hsd:issueDate>2021-03-04</hsd:issueDate>
                </hsd:ENC>
                <hsd:ENC>
                    <hsd:name>US4AK6ZQ</hsd:name>
                    <hsd:scale>40000</hsd:scale>
                    <hsd:edition>1</hsd:edition>
                    <hsd:updateApplicationDate>2020-09-03</hsd:updateApplicationDate>
                    <hsd:issueDate>2024-01-26</hsd:issueDate>
                </hsd:ENC>
                <hsd:comments />
            </dr:charts>
            <dr:shoalAndHazardousFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No shoals or potentially hazardous features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:shoalAndHazardousFeatures>
            <dr:chartedFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No charted features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:chartedFeatures>
            <dr:unchartedFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No uncharted features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:unchartedFeatures>
            <dr:channels>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No channels exist within the survey limits.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:channels>
        </dr:chartComparison>
        <dr:additionalResults>
            <dr:ATONS>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No Aids to navigation (ATONs) exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ATONS>
            <dr:maritimeBoundary>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No Maritime Boundary Points were assigned for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:maritimeBoundary>
            <dr:bottomSamples>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>The Project Instructions required 10 bottom samples for this survey. 10 were successfully acquired at geographically dispersed locations, with specific locations chosen in regards to the acquired multibeam backscatter. Most returned silt as primary constituents. Samples were examined, photographed, and then discarded overboard. An overview of their locations is shown below. Detailed results are provided in the project FFF.

Note that samples were not acquired in the "expansion" (northeast) part of the survey due to the required quantity having been already acquired in the originally assigned area.</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>Locations of bottom samples relative to the survey area.</hsd:caption>
                        <hsd:link>SupportFiles\Bottom_Sample_Locations.png</hsd:link>
                    </hsd:images>
                </hsd:results>
                <hsd:comments />
            </dr:bottomSamples>
            <dr:overheadFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No overhead features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:overheadFeatures>
            <dr:submarineFeatures>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>A charted cable transects the north part of the survey area, and was assigned for investigation. A 1 m surface created from the MBES data was created and examined. No sign of the cable was observed in the data. Note however the cable was observed in data in junctioning survey H13914 to the east; refer to the DR from that survey for more information.

It is recommended to be retained as charted in the FFF.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:submarineFeatures>
            <dr:platforms>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No platforms exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:platforms>
            <dr:ferryRoutesAndTerminals>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No ferry routes or terminals exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ferryRoutesAndTerminals>
            <dr:abnormalSeafloorEnviroCond>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No abnormal seafloor or environmental conditions exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:abnormalSeafloorEnviroCond>
            <dr:constructionOrDredging>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No present or planned construction or dredging exist within the survey limits.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:constructionOrDredging>
            <dr:newSurveyRecommendation>
                <hsd:results recommended="false">
                    <hsd:discussion>No new surveys or further investigations are recommended for this area.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:newSurveyRecommendation>
            <dr:ENCScaleRecommendation>
                <hsd:results recommended="false">
                    <hsd:discussion>No new ENC scales are recommended for this area.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ENCScaleRecommendation>
        </dr:additionalResults>
    </dr:resultsAndRecommendations>
    <dr:approvalSheet>
        <dr:statements>
            <dr: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.</dr:supervision>
            <dr: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.</dr:approval>
            <dr:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Hydrographic Survey Project Instructions, and Statement of Work. 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, if any, noted in the Descriptive Report.</dr:adequacyOfSurvey>
            <dr:additionalInfo xsi:nil="true" />
        </dr:statements>
        <dr:signingPersonnel>
            <hsd:approverName>Andrew Orthmann, CH</hsd:approverName>
            <hsd:approverTitle>Charting Program Manager</hsd:approverTitle>
            <hsd:approvalDate>2025-01-25</hsd:approvalDate>
        </dr:signingPersonnel>
        <dr:additionalReports>
            <hsd:reportName>Survey Outline Submittal</hsd:reportName>
            <hsd:reportDateSent>2024-11-11</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>Final Progress Report</hsd:reportName>
            <hsd:reportDateSent>2024-11-15</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>Trained Marine Mammal Observer Log</hsd:reportName>
            <hsd:reportDateSent>2024-12-02</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>Marine Mammal Sightings Forms</hsd:reportName>
            <hsd:reportDateSent>2024-12-02</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>NCEI Sound Speed Data Submittal</hsd:reportName>
            <hsd:reportDateSent>2024-12-23</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>Coast Pilot Report</hsd:reportName>
            <hsd:reportDateSent>2025-01-16</hsd:reportDateSent>
        </dr:additionalReports>
    </dr:approvalSheet>
</dr:descriptiveReport>