1. (1) Fuel producers can apply to obtain a carbon intensity for their transportation fuels by following the process under this section.

2. (2) Applicants seeking approval to use a carbon intensity that is currently approved by CARB or OR-DEQ must provide:

   1. (a) The application package submitted to CARB or OR-DEQ;
   2. (b) The Tier 1 or Tier 2 CA-GREET or OR-GREET calculator approved by CARB or OR-DEQ, and the WA-GREET 3.0 equivalent with the fuel transportation and distribution cells modified for that fuel's pathway to Washington;
   3. (c) The CARB or OR-DEQ pathway review report or staff summary for the approved fuel pathway;
   4. (d) Verified annual fuel pathway report or validated pathway application, if applicable and submitted to CARB or OR-DEQ;
   5. (e) A positive or qualified positive validation or verification statement for the pathway issued under CARB LCFS verification program required by California Code of Regulations, Title 17, § 95500, or the OR-DEQ CFP verification program under Division 272 of the Oregon Administrative Rules;
   6. (f) Any other supporting materials relating to the pathway, as requested by ecology; and

   7. (g) If the applicant is seeking to use a provisional pathway approved by CARB or OR-DEQ, then the applicant must submit to ecology the ongoing documentation it provides to CARB or OR-DEQ, and as required in subsection (6) of this section. The applicant must provide to ecology within 14 days:

      1. (i) Any additional documentation it has submitted to CARB or DEQ; and
      2. (ii) A notification of any changes to the status of its provisional pathway approved by CARB or OR-DEQ.

3. (3) General requirements. Applicants seeking to obtain a carbon intensity using either the Tier 1 or Tier 2 calculator must submit the following information:

   1. (a) Company name and full mailing address.
   2. (b) Company contact person's contact information including the name, title or position, phone number, mobile phone number, facsimile number, email address, and website address.
   3. (c) Facility name (or names if more than one facility is covered by the application).
   4. (d) Facility address (or addresses if more than one facility is covered by the application).
   5. (e) EPA-assigned facility ID for facilities covered by the RFS program.
   6. (f) Facility geographical coordinates (for each facility covered by the application).
   7. (g) Facility contact person's contact information including the name, title or position, phone number, mobile phone number, facsimile number, and email address.
   8. (h) Facility nameplate production capacity in million gallons per year for each facility covered by the application, or an equivalent figure for facilities that do not produce liquid fuels.
   9. (i) If applicable, consultant's contact information including the name, title or position, phone number, mobile phone number, facsimile number, email address, and website URL.
   10. (j) Declaration whether the applicant is applying for a carbon intensity for a Tier 1 or Tier 2 fuel.

4. (4) Tier 1. In addition to the items in subsection (3) of this section, applicants seeking to obtain a carbon intensity for a Tier 1 fuel using one of the simplified calculators must submit the following:

   1. (a) The applicable simplified calculator with all necessary inputs completed, following the instructions in the applicable manual (dated November 2022) for that calculator. The period covered shall be the most recent 24-month period of operation, or at least three months of operation for provision fuel pathway applications. All applicants using grid electricity must choose electrical generation mixes from among the subregions specified in the Simplified Tier 1 CI calculators, if applicable;
   2. (b) All documentation related to the approval and verification of the fuel pathway application from the jurisdiction and from the third-party verifier. This includes a positive verification statement from CARB or OR-DEQ approved verification body, stating that it has reviewed and validated all of the data used to form the inputs for the Tier 1 calculator submitted under (a) of this subsection, or the invoices and receipts for all forms of energy consumed in the production process, all fuel sales, all feedstock purchases, and all coproducts sold for the most recent 24 months of full commercial production, along with a summary of those invoices and receipts; and
   3. (c) The most recent RFS third-party engineering report, if one has been conducted for the facility.

5. (5) Tier 2. In addition to the items in subsection (3) of this section, applicants seeking to obtain a carbon intensity for a Tier 2 fuel using the full WA-GREET 3.0 model must first submit the information required in (b) through (h) of this subsection to ecology and request approval of their proposed approach for modeling the carbon intensity of their pathway or pathways. In response to such a submission, ecology may either approve it, deny it, or approve it with draft operating conditions that a verifier can use to determine the scope of the verification services they must provide. If ecology denies the submission, ecology must provide the applicant with an explanation why it was denied, and the applicant may resubmit information to seek an approval. Once the applicant gains ecology's initial approval, they may then seek verification of their application under the following:

   1. (a) A positive or qualified positive validation or verification statement from CARB or OR-DEQ approved verification body, stating that it has reviewed and validated all of the data used to form the inputs for the Tier 2 calculator submitted under (c) of this subsection, or the invoices and receipts for all forms of energy consumed in the production process, all fuel sales, all feedstock purchases, and all coproducts sold for the most recent 24 months of full commercial production, and a summary of those invoices and receipts;
   2. (b) The geographical coordinates of the fuel production facility;
   3. (c) A completed Tier 2 model;
   4. (d) Process flow diagrams that depict the complete fuel production process;
   5. (e) Applicable air permits issued for the facility;
   6. (f) A copy of the latest RFS third-party engineering report, if available;
   7. (g) A copy of the RFS fuel producer coproducts report; and
   8. (h) A life cycle analysis report that describes the fuel pathway and describes in detail the calculation of carbon intensity for the fuel. The report shall contain sufficient detail to allow staff to replicate the carbon intensity the applicant calculated. The applicant must describe all inputs to, and outputs from, the fuel production process that are part of the fuel pathway.

6. (6) Applicants seeking a provisional carbon intensity. If a fuel production facility has been in full commercial production for at least 90 days but less than 24 months, it can apply for a provisional carbon intensity.

   1. (a) The applicant shall submit operating records covering all periods of full commercial operation in accordance with subsections (2) through (5) of this section.
   2. (b) Ecology may approve the provisional carbon intensity under subsection (9) of this section.
   3. (c) At any time before the plant reaches a full 24 months of full commercial production, ecology may revise as appropriate the operational carbon intensity based on the required ongoing submittals or other information it learns.
   4. (d) If, after a plant has been in full commercial production for more than 24 months, the facility's operational carbon intensity is higher than the provisionally-certified carbon intensity, ecology will replace the certified carbon intensity with the operational carbon intensity in the WFRS and adjust the credit balance accordingly.
   5. (e) If the facility's operational carbon intensity appears to be lower than the certified carbon intensity, ecology will take no action. The applicant may petition ecology for a new carbon intensity that reflects the operational data. In support of such a petition, the applicant must submit a revised application packet that fully documents the requested reduction.

7. (7) Applicants employing co-processing at a petroleum refinery.

   1. (a) Applicants employing co-processing of biogenic feedstocks at a petroleum refinery must submit all information required under subsections (3) and (5) of this section.

   2. (b) For the renewable diesel or other renewable refinery product of the fuel, the applicant must also submit:

      1. (i) The planned proportions of biogenic feedstocks to be processed;
      2. (ii) A detailed methodology for the allocation of biogenic feedstocks to the renewable products; and
      3. (iii) The corresponding carbon intensities from each biogenic feedstock.
   3. (c) The allocation methodology for associating amount of the biogenic feedstocks to the production a unit of fuel shall be equivalent to allocation methodologies accepted in the federal and other states' similar programs, and will be subject to ecology approval and may be modified at ecology's discretion based on ongoing reporting of production data at the refinery.
   4. (d) Ecology may adjust the carbon intensities applied for under this section as it determines is appropriate.

8. (8) Temporary fuel pathway codes for fuels with indeterminate carbon intensities.

   1. (a) A registered party that has purchased a fuel without a carbon intensity must submit a request to ecology for permission to use a temporary fuel pathway code in (a)(i) or (ii) of this subsection that:

      1. (i) Already exists in Table 8 under WAC 173-424-900; or
      2. (ii) A fuel producer may also apply to ecology for approval to have a temporary fuel pathway code assigned to its facility. Ecology will review the request and post on its website the newly approved temporary pathway under subsection (11) of this section.

   2. (b) The request must:

      1. (i) Be submitted within 45 days after the end of the calendar quarter for which the applicant is seeking to use a temporary fuel pathway code; and
      2. (ii) Explain and document that the production facility is unknown or that the production facility is known but there is no approved fuel pathway code.
   3. (c) Temporary fuel pathway codes may be used for up to two calendar quarters. If more time is needed to obtain a carbon intensity, the party that obtained the temporary fuel pathway must submit an additional request to ecology for an extension of the authorization to use a temporary fuel pathway code.
   4. (d) If ecology grants a request to use a temporary fuel pathway code, credits and deficits may be generated subject to the quarterly reporting provisions in WAC 173-424-410.

9. (9) Review and approval process to use carbon intensities for fuels other than utility-specific electricity and renewable electricity with a deemed CI of zero under WAC 173-424-630.

   1. (a) For applications proposing to use fuel pathways approved by CARB or OR-DEQ, including provisional pathways, ecology will:

      1. (i) Confirm that the proposed fuel pathway is consistent with WA-GREET 3.0; and
      2. (ii) Review the materials submitted under subsection (2) of this section and request additional materials if necessary.

   2. (b) For applications proposing to use the Tier 1 or Tier 2 calculators, ecology may approve the application if it can:

      1. (i) Verify the energy consumption and other inputs.
      2. (ii) Replicate the calculator outputs; and

      3. (iii) Agree with the following in the application:

         1. (A) Its classification of its feedstock(s);
         2. (B) The scope of its lifecycle and, for Tier 2 applications, how the process has been modeled and if the carbon intensity values are scientifically defensible in the ecology's engineering and scientific judgment;
         3. (C) Any modifications to emissions factors, for Tier 2 fuels;
         4. (D) Any other aspects of the pathway(s) in the application that affect the carbon intensity value.

      4. (iv) For Tier 2 pathway applications, if ecology intends to approve an application, it first must:

         1. (A) Present a review report with a proposed carbon intensity value or values and operating conditions to the applicant or applicants. If the applicant or applicants accept the proposed review report, carbon intensity value(s) and operating conditions, ecology will post the review report and application on its website for a 14-day public comment period. Ecology staff will work with the applicant to aggregate and summarize any submitted data in order to ameliorate concerns regarding trade secrets included in the application. The aggregated data must still allow external stakeholders to understand the pathway(s) and carbon intensity value(s) that DEQ is proposing to approve; and
         2. (B) Based on comments received during that public comment period, ecology may move forward with approving the application as provided in this section, deny the application, request additional information from the applicant or applicants, or modify the review report. If ecology modifies the review report or receives additional information that has a material bearing on the proposed EER value, it will issue the modified review report and any affected supplemental materials for another round of public comment.
   3. (c) If ecology has approved or denied the application for a carbon intensity, ecology will notify the applicant of its determination.
   4. (d) Ecology may impose conditions in its approval of the carbon intensity. Conditions may include specific limitations, recordkeeping or reporting requirements, adherence to protocols to assure carbon reduction or sequestration claims, or operational conditions that ecology determines should apply to assure the ongoing accuracy of the approved carbon intensity. Failure to meet those conditions may result in the carbon intensity approval being revoked.

   5. (e) For applicants seeking a provisional pathway, ecology will specify the conditions used to establish the pathway.

      1. (i) In order to maintain an active provisional pathway eligible to generate credits, the applicant must file the annual fuel pathway report and seek third-party verification as required under WAC 173-424-820.
      2. (ii) At any point during the 24 months following the certification of a provisional pathway, ecology may revise as appropriate the CI score for the provisional pathway, and adjust any credits in the fuel reporting entity based on new information or a better understanding of the pathway.
      3. (iii) Ecology may remove the provisional status of the pathway after the applicant provides 24 months of operational data with a positive or qualified positive verification status, as required under WAC 173-424-800 through 173-424-850.
      4. (iv) For pathways that are not subject to verification, ecology may remove the provisional status upon review of 24 months of operational data demonstrating that the pathway data supports the provisional CI.

   6. (f) For a fuel pathway approved by CARB or OR-DEQ that ecology has approved for use in Washington, if at any time the pathway's approval is revoked by CARB or OR-DEQ then:

      1. (i) The fuel pathway holder must inform ecology within 14 days of the revocation and provide ecology with the documentation related to that decision.
      2. (ii) Upon ecology request, the fuel pathway holder must provide to ecology additional documentation.
      3. (iii) Ecology may at its discretion revoke its approval of the pathway's use in Washington at any time.
      4. (iv) If CARB or OR-DEQ modifies its approval of the pathway, then the fuel pathway holder must notify ecology of the modification not later than 14 days after CARB's or OR-DEQ modification and must provide to ecology any accompanying documentation the fuel pathway holder received from CARB or OR-DEQ.
      5. (v) Based on the underlying facts that led to CARB's and OR-DEQ's modification of the pathway's status, within 30 days ecology may modify its approval, take no action, or revoke its approval and will provide the fuel pathway holder with written notice of its decision.

   7. (g) In order to receive and maintain an active fuel pathway code, the producer of any fuel must:

      1. (i) Maintain an active registration with the AFP;
      2. (ii) Provide proof of delivery to Washington through a physical pathway demonstration in the quarter in which the fuel is first reported in the WFRS;

      3. (iii) Each fuel pathway holder must submit an annual fuel pathway report into the AFP no later than March 31st of each calendar year, and verification statements for fuel pathways no later than September 15th of each year. The annual fuel pathway report must include:

         1. (A) The certified version of the simplified WA-GREET or full WA-GREET calculator, as applicable, updated to include the most recent two calendar years of operational data;
         2. (B) The annual fuel pathway report for renewable electricity and hydrogen lookup table pathways, in lieu of the CI calculator, must include invoices or metering records substantiating the quantity of renewable or low-CI inputs procured from a qualifying source;

         3. (C) If the fuel or fuel production process involves biomethane or renewable electricity, the fuel producer must:

            1. (I) Provide the attestation regarding environmental attributes or proof of nongeneration or retirement of any RECs and RTCs as required by WAC 173-424-420 or 173-424-630 (4)(d); and
            2. (II) For biomethane injected into a natural gas common carrier pipeline, RTCs from the midwest renewable energy tracking systems (M-RETS) or another ecology-recognized renewable thermal tracking system are required to be retired and used instead of an attestation and the specific volume of biomethane claimed as being used in the fuel production process must have been injected into the pipeline in the current or prior quarter as the fuel is being produced. Biomethane can only be claimed in this manner in a fuel pathway application as the feedstock for CNG, LNG, L-CNG or hydrogen production, and cannot be claimed as an energy source for another fuel production process.
         4. (D) Any fuel pathway holder, including a joint applicant, who is not subject to site visits by a third-party verifier, whose fuel pathway involves the use of renewable or low-CI process energy, must submit invoices for that energy to the AFP. Additionally, for any on-site or directly connected renewable electricity that is used to reduce the carbon intensity of electricity used as a transportation fuel or hydrogen production via electrolysis, the pathway holder must upload records demonstrating that any renewable energy certificates generated were retired in WREGIS or another comparable, recognized REC tracking system for the purpose of lowering the certified CI, or for credit generation. Any offsite source of renewable electricity must meet the requirements under WAC 173-424-630(5);
         5. (E) Any temporally variable information that was requested or required by ecology to be included in the initial application as supplemental information, or any required data or documentation listed in the pathway's operating conditions. The information required to be submitted under this subsection must cover the same time period as the updated WA-GREET model required under (g)(iii)(A) of this subsection;
         6. (F) If the verified operational CI as calculated from the operational data covering the prior two calendar years of production is found to be lower than the certified CI, and a positive verification statement is issued for this period, the fuel pathway holder may elect to keep the original certified CI, or may request to replace the certified CI with the verified operational CI and a new margin of safety. The new certified CI will take effect for the following reporting year. The fuel pathway holder may elect to add a margin of safety to the new certified CI, and must submit an attestation that the new CI can be maintained through the next reporting period with the acknowledgment that exceeding the newly certified CI in subsequent annual reports or verifications is a violation of the requirements of this chapter; and
      4. (iv) Comply with the requirements of this chapter. Failure to timely submit an annual fuel pathway report or a required verification statement for a facility's pathways will result in the deactivation of those pathways; and
      5. (v) If a pathway employs carbon capture and sequestration, the fuel pathway holder or joint applicant must submit annual reports of greenhouse gas emissions reductions, project operations, and ongoing monitoring results. Reports must include measurements of relevant parameters sufficient to ensure that the quantification and documentation of CO₂ sequestered is replicable and verifiable. Ecology may specify a protocol for measuring and reporting such information in its approval of such an application.
   8. (h) If ecology determines the proposal for the carbon intensity has not met the criteria in (b) of this subsection, ecology will notify the applicant that the proposal is denied and identify the basis for the denial.
   9. (i) Ecology may modify an approved fuel pathway's CI or approval conditions upon receipt of a verification statement that shows that the verified operational CI is higher than the certified CI.
   10. (j) Any applicant may include a margin of safety in its application which will increase its certified CI in order to account for potential process variability and to reduce the risk that it will violate this chapter by having its operational CI exceed its certified CI.
   11. (k) Ecology may prioritize the review of fuel pathway applications according to the date the application is submitted, the application deemed complete date, and the potential GHG emission reduction potential.

   12. (l) If the verified operational CI is found to be greater than the certified CI (including provisionally certified and/or an associated temporary pathway CI) for the same feedstock-fuel combination processed at the same facility:

       1. (i) Ecology will invalidate the excess credits generated from the CI exceedance for the applicable compliance year in WFRS account of the associated fuel reporting entities.
       2. (ii) Beginning with the 2026 fuel transactions reporting year, a fuel pathway holder for a nonprovisional fuel pathway generates a deficit obligation following a verified CI exceedance. The fuel pathway holder generates a deficit obligation following the verified CI exceedance, which is calculated as specified below in (l)(iii) of this subsection.

       3. (iii) The deficit obligation or quantity of deficits generated due to the CI exceedance is calculated as four times the difference between the verified operational fuel pathway CI and the reported CI, multiplied by the quantity of fuel reporting using that fuel pathway during the applicable year. Deficits will be calculated using the following equation:

          [if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]

          	Where:
          		[if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]	is the number of calculated deficits from CI exceedance;
          		[if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]	is the verified operational fuel pathway CI for a given compliance period;
          		[if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]	is the certified CI in WFRS under which the fuel was reported;
          		E	is the reported fuel under a given certified fuel pathway in Megajoules;
          		C	is a factor used to convert credits/deficits to units of metric tons from gCO2e and has the value of:

          	C	=	1 × 106	(MT)
          	(gCO2e)

       4. (iv) Any pathway holder generating deficits following a verified CI exceedance must satisfy the compliance demonstration requirements in WAC 173-424-500.
       5. (v) Fuel pathway holders who demonstrate that the verified operational CI exceedances are solely due to calculator updates (for CI calculators using CA-GREET 4.0 or OR-GREET 4.0 and the updated Tier 1 calculators) are exempt from the deficit obligation specified in (l)(iii) of this subsection. To make this demonstration, fuel pathway holders must submit both CA-GREET 3.0 and CA-GREET 4.0 or OR-GREET 3.0 and OR-GREET 4.0 modeling tools populated with the operational data for the same reporting period for annual verification in the AFP.
       6. (vi) Notwithstanding (l)(v) of this subsection, the fuel pathway holder of a pathway with 24 months of operational data is out of compliance, and ecology may take additional enforcement action.

   13. (m) Credit true up after annual verification. Beginning with the 2025 annual fuel pathway report data reporting year, ecology shall perform credit true up for a fuel pathway, including a temporary pathway used by an entity that subsequently receives fuel pathway certification for the associated production facility, that has a lower verified operational CI upon receiving a positive or qualified positive verification statement for the associated annual fuel pathway report and quarterly fuel transactions reports, notwithstanding the prohibition on retroactive credit generation in WAC 173-424-430(4).

       1. (i) To implement this true up, ecology will calculate an equivalent number of credits representing the difference between the reported CI and the verified operational CI from annual fuel pathway reports for each fuel pathway code reported with nonliquid transaction types and with the following liquid fuel transaction types "production in Washington," "production for import," and "import" during a compliance year, and place those credits in the account of each appropriate fuel reporting entity after September 15th for the prior compliance year. Only reporting quarters for which complete operational data are reported in the applicable AFPR are eligible for credit true up of a temporary fuel pathway.

       2. (ii) The credits will be calculated according to the following equation:

          [if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]

          	Where:
          		[if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]	is the number of credits representing the difference between the reported CI and verified operational CI for each fuel pathway code;
          		[if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]	is the number of credits calculated in the verified operational CI, instead of the reported CI; and
          		[if IE 9]><video style="display: none;"><![endif][if IE 9]></video><![endif]	is the number of credits calculated using the reported CI.

   14. (n) Utility-specific carbon intensities or utility renewable electricity products for alternative jet fuel and alternative marine fuel production using electrolytic hydrogen as a feedstock.

       1. (i) Producers of alternative jet fuel, sustainable aviation fuel, or alternative marine fuel may use a utility renewable electricity product or utility-specific carbon intensity for electrolysis process energy in their pathway applications or annual fuel pathway reports through December 31, 2037. After that date, producers must use:

          1. (A) The statewide grid average; or
          2. (B) Directly connected renewable electricity.

       2. (ii) Through December 31, 2037, to claim a low-CI or zero-CI electricity for utility renewable electricity product or utility-specific carbon intensity, a registered party must:

          1. (A) Provide any documentation or agreement between the reporting party and the relevant electric utility for the low-CI or zero-CI utility renewable electricity product;
          2. (B) Obtain written approval from ecology before submitting the fuel pathway application or annual fuel pathway report to claim a low-CI or zero-CI electricity using the utility renewable electricity product or utility-specific carbon intensity; and
          3. (C) Register in WREGIS any RECs used for low-CI or zero-CI utility renewable electricity product or utility-specific carbon intensity claims, and demonstrate the RECs are either retired in the CFS program account each quarter or demonstrate it is retired in the Washington utilities and transportation commission or Washington department of commerce program account.

       3. (iii) During the period specified under (n)(i) of this subsection, to claim a low-CI or zero-CI electricity using utility renewable electricity product (otherwise known as a rate schedule) or utility specific carbon intensity for alternative jet fuel or alternative marine fuel production, the registered party must demonstrate to ecology that:

          1. (A) The utility renewable electricity product (rate schedule) was negotiated prior to December 31, 2025, or demonstrate (B) and (C) below:
          2. (B) Electricity provided to the registered party under the terms of the rate schedule is generated entirely from renewable electricity generation facilities located in Washington, Oregon, or Idaho that commenced operations on or after January 1, 2019, or from efficiency improvements made on or after January 1, 2019. Any incremental hydroelectric generation must meet the conditions specified in RCW 19.405.040 (1)(d) to be eligible.
          3. (C) The utility's main utility-specific carbon intensity of electricity, after reducing the estimated amount of renewable electricity to be supplied under utility renewable electricity product (rate schedule), is below the carbon intensity of the statewide average electricity based on the latest annual fuel mix disclosure report.

10. (10) Completeness determination process.

    1. (a) Within one month after receiving a fuel pathway application using the Tier 1 or Tier 2 calculator, ecology will advise in writing whether:

       1. (i) The proposal is complete; or
       2. (ii) The application is incomplete, in which case ecology identifies the deficiencies.
    2. (b) The applicant may submit supplemental information to correct the ecology identified deficiencies. Ecology has 30 calendar days to determine if the supplemental submittal is complete, or to notify the party and identify the continued deficiencies. If the applicant is unable to achieve a complete application within 180 days of ecology's receipt of the original application, the application will be denied on that basis, and the applicant will be informed in writing.
    3. (c) Ecology releases the completed Tier 2 pathway applications for validation.

11. (11) Issuing additional substitute and temporary fuel pathway codes.

    1. (a) For new fuels or new fuel blends being used in Washington state, registered parties may request ecology for an additional fuel pathway code that can be used in the same manner as those in Table 7 or 8 (substitute or temporary pathway codes) under WAC 173-424-900.
    2. (b) Ecology may approve such substitute or temporary pathway codes if it concludes they are technically sound and supported by appropriate evidence. If any are approved, ecology will post these additional pathway codes in the WFRS and on its public website for the clean fuels program.

    3. (c) All of the following requirements apply to such requests:

       1. (i) Requests must be made in writing to ecology.

       2. (ii) If ecology concludes the proposed pathway may be technically sound and supported by appropriate evidence, then it will post the proposed new substitute or temporary pathway codes on its website and take comments for:

          1. (A) Fourteen calendar days in the case of a substitute fuel pathway code; or
          2. (B) Forty-five calendar days in the case of a temporary fuel pathway code.
       3. (iii) Ecology will consider any comments received, make any modifications, if necessary, and make a final decision on the proposed pathway.
       4. (iv) Ecology may approve the fuel pathway and publish it on its website, if ecology concludes the proposed pathway is technically sound and supported by appropriate evidence.
    4. (d) Any newly approved substitute or temporary fuel pathway code will be effective for use in the quarter in which it is approved.

12. (12) Measurement accuracy.

    1. (a) Calibration requirement. All measurement devices that log or record data for use in a fuel pathway application must comply with the manufacturer-recommended calibration frequency and precision requirements. If manufacturer recommendations are not provided, the measurement devices must be calibrated at least every six years.

    2. (b) Requests to postpone calibration. For units and processes that operate continuously with infrequent outages, it may not be possible to meet manufacturer-recommended calibration deadlines for measurement devices. In such cases, the owner or operator may submit a written request to ecology to postpone calibration or inspection until the next scheduled maintenance outage. Such postponements are subject to the procedures of (b)(ii)(A) and (B) of this subsection and must be documented in the monitoring plan required under WAC 173-424-400.

       1. (i) A written request for postponement must be submitted to ecology not less than 30 days before the required calibration, recalibration or inspection date. Ecology may request additional documentation to validate the operator's claim that the device meets the accuracy requirements of this section. The operator shall provide any additional documentation to ecology within 10 business days of a request for documentation.

       2. (ii) The request must include:

          1. (A) The date of the required calibration, recalibration, or inspection;
          2. (B) The date of the last calibration or inspection;
          3. (C) The date of the most recent field accuracy assessment, if applicable;
          4. (D) The results of the most recent field accuracy assessment, if applicable, clearly indicating a pass/fail status;
          5. (E) The proposed date for the next field accuracy assessment, if applicable;
          6. (F) The proposed date for calibration, recalibration, or inspection which must be during the time period of the next scheduled shutdown. If the next shutdown will not occur within three years, this must be noted and a new request must be received every three years until the shutdown occurs and the calibration, recalibration or inspection is completed; and

          7. (G) A description of the meter or other device including, at a minimum, the:

             1. (I) Make and model;
             2. (II) Installation date;
             3. (III) Location;
             4. (IV) Parameter measured by the meter or other device, including the rate of data capture;
             5. (V) Description of how data from the meter or other device is used in a fuel pathway;
             6. (VI) Calibration or inspection procedure;
             7. (VII) Reason for delaying the calibration or inspection;
             8. (VIII) Proposed method to ensure that the precision requirements listed by the manufacturer are upheld; and
             9. (IX) The contact details for an individual at the fuel production facility who can answer questions about the meter or other device.
       3. (iii) Ecology will approve or deny the request at its discretion based on whether or not it concludes that the device's calibration is reasonably reliable.

13. (13) Missing data provisions.

    1. (a) Meter record, accuracy, or calibration requirements not met. If a measurement device is not functional, not calibrated within the time period recommended by the manufacturer, or fails a field accuracy assessment, the fuel production facility operator must otherwise demonstrate to a verifier or ecology that the reported data are accurate within +/- five percent. The following requirements apply to such demonstration:

       1. (i) If the operator can demonstrate to the verifier or ecology staff that reported data are accurate, the data are acceptable. The entity must then provide a detailed plan describing when the measurement device will be brought into calibration. This plan is subject to ecology approval; and
       2. (ii) If the operator cannot demonstrate to the verifier or ecology that reported data are accurate, the data is not acceptable and the missing data provisions in (b) of this subsection apply.
    2. (b) Missing data provisions. If missing data exists, the entity must submit for ecology approval an alternate method of reporting the missing data. Alternate methods shall be evaluated on a case-by-case basis for reasonableness and continuity with the rest of the dataset. Ecology may choose to require a more conservative approach to the missing data if it is concerned that the alternative method may understate actual life cycle emissions associated with the fuel or fuels produced by the facility.
    3. (c) Force majeure events. In the event of a facility shutdown or disruption drastically affecting production attributable to a force majeure event, the fuel pathway applicant or holder must notify ecology. Ecology may require the reporting entity to provide documentation to support the force majeure event timeline.
14. (14) Biomethane applications. In addition to the other requirements of this rule, for any fuel pathway where biomethane is being injected into a natural gas common carrier pipeline to be reported in the CFP using book and claim accounting, the fuel pathway holder, fuel producer, or both must ensure that no other party can make a claim on the specific biomethane attributes that are being used in the CFP. If the biomethane is being injected into the pipe of a local distribution company, the fuel producer must have an agreement with that company along with any other purchaser of the physical gas that they will not make any claims on the biomethane reported through book and claim in this program. That agreement must be submitted at the time of the fuel pathway application or in the next annual fuel pathway report if the fuel pathway is currently certified.
15. (15) For nonprovisional pathways. If a fuel pathway's operational CI is found to be greater than its certified CI, the fuel pathway holder is out of compliance with this chapter and may be subject to investigation and enforcement by ecology.

16. (16) Avoided methane crediting.

    1. (a) A fuel pathway that utilizes biomethane from dairy cattle or swine manure digestion may be certified with a CI that reflects the reduction of greenhouse gas emissions achieved by the voluntary capture of methane, provided that:

       1. (i) A biogas control system, or digester, is used to capture biomethane from manure management on dairy cattle and swine farms that would otherwise be vented to the atmosphere as a result of livestock operations from those farms.
       2. (ii) The baseline quantity of avoided methane reflected in the CI calculation is additional to any regulatory requirement for the capture and destruction of biomethane.
       3. (iii) The dairy cattle or swine farm has historically used an anaerobic lagoon to manage and treat waste from livestock operations and has not introduced liquid or slurry manure management in the five years preceding the fuel pathway application.
       4. (iv) To maintain eligibility for avoided methane emissions credits under this program, the facility providing biomethane to the pathway holder should remain in compliance with all applicable federal, state, and local environmental regulations including, but not limited to, limitations on applicable air quality emissions, water quality and discharges, solid and hazardous waste management, climate change or greenhouse gas emissions, odor/nuisance management, concentrated animal feeding operations, and nutrient management and land applications. If a facility is found in violation of any of these applicable environmental regulations by a regulatory authority with jurisdiction, the pathway holder may be deemed ineligible to generate avoided methane emissions credits until the facility demonstrates that they have remedied the violation to the satisfaction of ecology, or ecology is satisfied that the facility is taking adequate steps to remedy the violation. Ecology will formally notify the pathway holder if a facility is deemed ineligible to generate avoided methane credits pursuant to this subsection. If ecology determines the violation has been remedied or that the facility is taking adequate steps to remedy, the pathway holder may resume generating avoided methane credits. Ecology will not issue retroactive credits for methane emissions avoided by the facility during the period of noncompliance with the aforementioned requirements. However, the pathway holder is eligible to generate CFS credits with a revised carbon intensity score, without credits for avoided methane emissions, during the facility's noncompliance period. This requirement applies to facility operations related to dairy or swine manure handling systems, anaerobic digestion systems, systems upgrading biogas to renewable natural gas, and electricity generation from biogas.

    2. (b) A fuel pathway that utilizes an organic material may be certified with a CI that reflects the reduction of greenhouse gas emissions achieved by the voluntary diversion from decomposition in a landfill and the associated fugitive methane emissions, provided that:

       1. (i) The organic material that is used as a feedstock would otherwise have been disposed of by landfilling, and the diversion is additional to any legal or regulatory requirement for the diversion of organics from landfill disposal.
       2. (ii) Any degradable carbon that is not converted to fuel is subsequently treated in an aerobic system or otherwise is prevented from release as fugitive methane. Upon request, the applicant must demonstrate that emissions are not significant beyond the system boundary of the fuel pathway.
       3. (iii) The baseline quantity of avoided methane reflected in the CI calculation is additional to any legal or regulatory requirement for the avoidance or capture and destruction of biomethane.

    3. (c) Carbon intensities that reflect avoided methane emissions from dairy or swine manure pathways, as described in (a) of this subsection, or organic waste pathways as described in (b) of this subsection, are subject to the following requirements for credit generation:

       1. (i) The avoided methane crediting period for projects that break ground between January 1, 2023, and December 31, 2029, is limited to two 10-year periods, counting from the quarter following ecology approval of the pathway application.

       2. (ii) The avoided methane crediting period for projects that break ground on or after January 1, 2030, will be offered as established in (A) and (B) below.

          1. (A) For pathways for bio-CNG, bio-LNG, and bio-L-CNG vehicles is used CNG vehicles, ecology shall only approve avoided methane crediting through December 31, 2040.
          2. (B) For pathways where biomethane is used to produce hydrogen, electricity, renewable diesel, alternative jet fuel, or alternative marine fuel, ecology shall only approve avoided methane crediting through December 31, 2045.

       3. (iii) The avoided methane crediting period for projects that started operations to produce biomethane before January 1, 2023, is subject to the following conditions:

          1. (A) The crediting period for a facility that started operation in 2022 is limited to 19 years.
          2. (B) The crediting period reduces by one year for each year that a facility started operations to produce biomethane prior to January 1, 2023. For example, a facility that started operation in 2020 is eligible for avoided methane credits for 17 years.
          3. (C) Facilities that started operations to produce biomethane before 2003 are not eligible for avoided methane crediting.

    4. (d) Incremental biomethane production capacity. Avoided methane crediting applies to biomethane production capacity expansion projects in existing facilities described in (a) and (b) of this subsection, provided the pathway applicant provided robust evidence to ecology to establish:

       1. (i) The baseline biomethane production capacity; and
       2. (ii) The biomethane production capacity from the expansion project.
    5. (e) Notwithstanding (a) and (b) of this subsection, in the event that any law, regulation, or legally binding mandate requiring either greenhouse gas emission reductions from manure methane emissions from livestock and dairy projects or diversion of organic material from landfill disposal comes into effect during a project's crediting period, then the project is only eligible to receive avoided methane credits for the remainder of the project's current crediting period. The project may not request any additional avoided methane crediting periods.
    6. (f) Notwithstanding the above, projects that have generated compliance offset credits under WAC 173-446-500 through 173-446-595 may apply to receive CFS credits. However, the avoided methane crediting period for such projects is aligned with the crediting period for compliance offset credits and does not reset when the project is certified under the CFS.

[Statutory Authority: Chapter 70A.535 RCW and RCW 70A.02.060. WSR 25-21-106 (Order 23-10), s 173-424-610, filed 10/20/25, effective 11/20/25. Statutory Authority: Chapter 70A.535 RCW. WSR 22-24-004 (Order 21-04), § 173-424-610, filed 11/28/22, effective 12/29/22.]