(a) If you own or operate a new or reconstructed affected source that must meet the emission limitation, you must submit a semiannual compliance report according to Table 6 to this subpart by the applicable dates specified in paragraphs (a)(1) through (6) of this section, unless the Administrator has approved a different schedule.

(1) The first semiannual compliance report must cover the period beginning on the compliance date specified in §63.9295 and ending on June 30 or December 31, whichever date is the first date following the end of the first calendar half after the compliance date specified in §63.9295.

(2) The first semiannual compliance report must be postmarked or delivered no later than July 31 or January 31, whichever date follows the end of the first calendar half after the compliance date that is specified in §63.9295.

(3) Each subsequent semiannual compliance report must cover the semiannual reporting period from January 1 through June 30 or the semiannual reporting period from July 1 through December 31.

(4) Each subsequent semiannual compliance report must be postmarked or delivered no later than July 31 or January 31, whichever date is the first date following the end of the semiannual reporting period.

(5) For each new or reconstructed engine test cell/stand that is subject to permitting regulations pursuant to 40 CFR part 70 or 71, and if the permitting authority has established the date for submitting semiannual reports pursuant to 40 CFR 70.6(a)(3)(iii)(A) or 40 CFR 71.6(a)(3)(iii)(A), you may submit the first and subsequent compliance reports according to the dates the permitting authority has established instead of according to the dates in paragraphs (a)(1) through (4) of this section.

(6) For affected sources prior to December 1, 2020, if you had an SSM of a control device or associated monitoring equipment during the reporting period and you took actions consistent with your SSMP, the compliance report must include the information in paragraphs §63.10(d)(5)(i).

(7) Beginning on December 1, 2020, submit all semiannual compliance reports following the procedure specified in paragraph (g) of this section.

(b) If there is no deviation from the applicable emission limitation and the CEMS or CPMS was not out-of-control, according to §63.8(c)(7), the semiannual compliance report must contain the information described in paragraphs (b)(1) through (4) of this section.

(1) Company name and address.

(2) Statement by a responsible official, with that official's name, title, and signature, certifying the truth, accuracy, and completeness of the content of the report.

(3) Date of report and beginning and ending dates of the reporting period.

(4) A statement that no deviation from the emission limit occurred during the reporting period and that no CEMS or CPMS was out-of-control, according to §63.8(c)(7).

(c) For each deviation from an emission limit, the semiannual compliance report must include the information in paragraphs (b)(1) through (3) of this section and the information included in paragraphs (c)(1) through (4) of this section, except that on and after December 1, 2020 the semiannual compliance report must also include the information included in paragraph (c)(5) of this section.

(1) The date and time that each deviation started and stopped.

(2) The total operating time of each new or reconstructed engine test cell/stand during the reporting period.

(3) A summary of the total duration of the deviation during the reporting period (recorded in 4-hour periods), and the total duration as a percent of the total operating time during that reporting period.

(4) A breakdown of the total duration of the deviations during the reporting period into those that are due to control equipment problems, process problems, other known causes, and other unknown causes.

(5) An estimate of the quantity of each regulated pollutant emitted over any emission limit, and a description of the method used to estimate the emissions.

(d) For each CEMS or CPMS deviation, the semiannual compliance report must include the information in paragraphs (b)(1) through (3) of this section and the information included in paragraphs (d)(1) through (10) of this section, except that on and after December 1, 2020, the semiannual compliance report must also include the information included in paragraph (d)(11) of this section.

(1) The date and time that each CEMS or CPMS was inoperative except for zero (low-level) and high-level checks.

(2) The date and time that each CEMS or CPMS was out-of-control including the information in §63.8(c)(8).

(3) A summary of the total duration of CEMS or CPMS downtime during the reporting period (reported in 4-hour periods), and the total duration of CEMS or CPMS downtime as a percent of the total engine test cell/stand operating time during that reporting period.

(4) A breakdown of the total duration of CEMS or CPMS downtime during the reporting period into periods that are due to monitoring equipment malfunctions, nonmonitoring equipment malfunctions, quality assurance/quality control calibrations, other known causes and other unknown causes.

(5) The monitoring equipment manufacturer(s) and model number(s) of each monitor.

(6) The date of the latest CEMS or CPMS certification or audit.

(7) The date and time period of each deviation from an operating limit in Table 2 to this subpart; date and time period of any bypass of the add-on control device; and whether each deviation occurred during a period of SSM or during another period.

(8) A summary of the total duration of each deviation from an operating limit in Table 2 to this subpart, each bypass of the add-on control device during the semiannual reporting period, and the total duration as a percent of the total source operating time during that semiannual reporting period.

(9) A breakdown of the total duration of the deviations from the operating limits in Table 2 to this subpart and bypasses of the add-on control device during the semiannual reporting period by identifying deviations due to startup, shutdown, control equipment problems, process problems, other known causes, and other unknown causes.

(10) A description of any changes in CEMS, CPMS, or controls since the last reporting period.

(11) The total operating time of each new or reconstructed engine test cell/stand during the reporting period.

(e) Prior to December 1, 2020, if you had an SSM of a control device or associated monitoring equipment during the semiannual reporting period that was not consistent with your SSMP, you must submit an immediate SSM report according to the requirements in §63.10(d)(5)(ii).

(f) Within 60 days after the date of completing each performance test or performance evaluation required by this subpart, you must submit the results of the performance test following the procedures specified in paragraphs (f)(1) through (3) of this section.

(1) Data collected or performance evaluations of CMS measuring relative accuracy test audit (RATA) pollutants using test methods supported by the EPA's Electronic Reporting Tool (ERT) as listed on the EPA's ERT website (https://www.epa.gov/electronic-reporting-air-emissions/electronic-reporting-tool-ert) at the time of the test. Submit the results of the performance test or performance evaluation to the EPA via the Compliance and Emissions Data Reporting Interface (CEDRI), which can be accessed through the EPA's Central Data Exchange (CDX) (https://cdx.epa.gov/). The data must be submitted in a file format generated through the use of the EPA's ERT. Alternatively, you may submit an electronic file consistent with the extensible markup language (XML) schema listed on the EPA's ERT website.

(2) Data collected or performance evaluations of CMS measuring RATA pollutants using test methods that are not supported by the EPA's ERT as listed on the EPA's ERT website at the time of the test. The results of the performance test or performance evaluation must be included as an attachment in the ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website. Submit the ERT generated package or alternative file to the EPA via CEDRI.

(3) If you claim some of the information submitted under paragraph (f) of this section is CBI, you must submit a complete file, including information claimed to be CBI, to the EPA. The file must be generated through the use of the EPA's ERT or an alternate electronic file consistent with the XML schema listed on the EPA's ERT website. Submit the file on a compact disc, flash drive, or other commonly used electronic storage medium and clearly mark the medium as CBI. Mail the electronic medium to U.S. EPA/OAQPS/CORE CBI Office, Attention: Group Leader, Measurement Policy Group, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. The same file with the CBI omitted must be submitted to the EPA via the EPA's CDX as described in paragraph (f)(1) of this section.

(g) If you are required to submit reports following the procedure specified in this paragraph, you must submit reports to the EPA via CEDRI, which can be accessed through the EPA's CDX (https://cdx.epa.gov/). You must use the appropriate electronic report template on the CEDRI website (https://www.epa.gov/electronic-reporting-air-emissions/compliance-and-emissions-data-reporting-interface-cedri) for this subpart. The report must be submitted by the deadline specified in this subpart, regardless of the method in which the report is submitted. If you claim some of the information required to be submitted via CEDRI is CBI, submit a complete report, including information claimed to be CBI, to the EPA. The report must be generated using the appropriate form on the CEDRI website. Submit the file on a compact disc, flash drive, or other commonly used electronic storage medium and clearly mark the medium as CBI. Mail the electronic medium to U.S. EPA/OAQPS/CORE CBI Office, Attention: Group Leader, Measurement Policy Group, MD C404-02, 4930 Old Page Rd., Durham, NC 27703. The same file with the CBI omitted must be submitted to the EPA via the EPA's CDX as described earlier in this paragraph.

(h) If you are required to electronically submit a report through CEDRI in the EPA's CDX, you may assert a claim of EPA system outage for failure to timely comply with the reporting requirement. To assert a claim of EPA system outage, you must meet the requirements outlined in paragraphs (h)(1) through (7) of this section.

(1) You must have been or will be precluded from accessing CEDRI and submitting a required report within the time prescribed due to an outage of either the EPA's CEDRI or CDX systems.

(2) The outage must have occured within the period of time beginning five business days prior to the date that the submission is due.

(3) The outage may be planned or unplanned.

(4) You must submit notification to the Administrator in writing as soon as possible following the date you first knew, or through due diligence should have known, that the event may cause or has caused a delay in reporting.

(5) You must provide to the Administrator a written description identifying:

(i) The date(s) and time(s) when CDX or CEDRI was accessed and the system was unavailable;

(ii) A rationale for attributing the delay in reporting beyond the regulatory deadline to EPA system outage;

(iii) Measures taken or to be taken to minimize the delay in reporting; and

(iv) The date by which you propose to report, or if you have already met the reporting requirement at the time of the notification, the date you reported.

(6) The decision to accept the claim of EPA system outage and allow an extension to the reporting deadline is solely within the discretion of the Administrator.

(7) In any circumstance, the report must be submitted electronically as soon as possible after the outage is resolved.

(i) If you are required to electronically submit a report through CEDRI in the EPA's CDX, you may assert a claim of force majeure for failure to timely comply with the reporting requirement. To assert a claim of force majuere, you must meet the requirements outlined in paragraphs (i)(1) through (5) of this section.

(1) You may submit a claim if a force majeure event is about to occur, occurs, or has occurred or there are lingering effects from such an event within the period of time beginning five business days prior to the date the submission is due. For the purposes of this section, a force majeure event is defined as an event that will be or has been caused by circumstances beyond the control of the affected facility, its contractors, or any entity controlled by the affected facility that prevents you from complying with the requirement to submit a report electronically within the time period prescribed. Examples of such events are acts of nature (e.g., hurricanes, earthquakes, or floods), acts of war or terrorism, or equipment failure or safety hazard beyond the control of the affected facility (e.g., large scale power outage).

(2) You must submit notification to the Administrator in writing as soon as possible following the date you first knew, or through due diligence should have known, that the event may cause or has caused a delay in reporting.

(3) You must provide to the Administrator:

(i) A written description of the force majeure event;

(ii) A rationale for attributing the delay in reporting beyond the regulatory deadline to the force majeure event;

(iii) Measures taken or to be taken to minimize the delay in reporting; and

(iv) The date by which you propose to report, or if you have already met the reporting requirement at the time of the notification, the date you reported.

(4) The decision to accept the claim of force majeure and allow an extension to the reporting deadline is solely within the discretion of the Administrator.

(5) In any circumstance, the reporting must occur as soon as possible after the force majeure event occurs.

[68 FR 28785, May 27, 2003, as amended at 85 FR 34346, June 3, 2020]