Title 40

SECTION 63.9050

63.9050 What reports must I submit and when

§ 63.9050 What reports must I submit and when?

(a) You must submit a compliance report that includes the information in paragraphs (c) through (e) of this section, as applicable, as specified in table 6 to this subpart.

(b) Unless the Administrator has approved a different schedule for submission of reports under § 63.10(a), you must submit each report according to paragraphs (b)(1) through (5) of this section.

(1) The first compliance report must cover the period beginning on the compliance date that is specified for your affected source in § 63.8995 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 that is specified for your source in § 63.8995 (i.e., June 30, 2006, for sources existing on April 17, 2006).

(2) The first 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 for your affected source in § 63.8995 (i.e., July 31, 2006, for sources existing on April 17, 2006).

(3) Each subsequent 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 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 affected source that is subject to permitting regulations pursuant to 40 CFR part 70 or 71, and if the permitting authority has established dates for submitting semiannual reports pursuant to 40 CFR 70.6 (a)(3)(iii)(A) or 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 (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) For existing sources and for new or reconstructed sources for which construction or reconstruction commenced after April 17, 2003, but before February 5, 2019, before October 13, 2020, if you had a startup, shutdown, or malfunction during the reporting period and you took actions consistent with your startup, shutdown, and malfunction plan, the compliance report must include the information in § 63.10(d)(5)(i). A startup, shutdown, and malfunction plan and the information in § 63.10(d)(5)(i) is not required after October 13, 2020.

(5) For existing sources and for new or reconstructed sources which commenced construction or reconstruction after April 17, 2003, but before February 5, 2019, before October 13, 2020, if there are no deviations from any emission limitations that apply to you, a statement that there were no deviations from the emission limitations during the reporting period.

(6) If there were no periods during which the CMS was out-of-control in accordance with the monitoring plan, a statement that there were no periods during which the CMS was out-of-control during the reporting period.

(7) Verification that you continue to use the equipment LDAR plan and information that explains any periods when the procedures in the plan were not followed and the corrective actions were not taken.

(8) If you did not make revisions to your site-specific monitoring plan and/or LDAR plan during the reporting period, a statement that you did not make any revisions to your site-specific monitoring plan and/or LDAR plan during the reporting period. If you made revisions to your site-specific monitoring plan and/or LDAR plan during the reporting period, a copy of the revised plan.

(9) If you meet the outlet concentration limit in table 1 to this subpart without the use of a control device for any emission point, verification that you have not made any process changes that could reasonably be expected to increase the outlet concentration since your most recent performance test for that emission point.

(10) The information specified in paragraphs (c)(10)(i) and (ii) of this section for those planned routine maintenance operations that caused or may cause an HCl storage tank control device not to meet the emission limits in table 1 to this subpart, as applicable.

(i) A description of the planned routine maintenance that was performed for each HCl storage tank control device during the reporting period. This description shall include the type of maintenance performed and the total number of hours during the reporting period that the HCl storage tank control device did not meet the emission limits in table 1 to this subpart, as applicable, due to planned routine maintenance.

(ii) A description of the planned routine maintenance that is anticipated to be performed for each HCl storage tank control device during the next reporting period. This description shall include the type of maintenance necessary, planned frequency of maintenance, and lengths of maintenance periods.

(d) For each deviation from an emission limitation occurring at an affected source where you are using a continuous monitoring system (CMS) to comply with the emission limitation in this subpart, you must include the information in paragraphs (c)(1) through (6) of this section and the following information in paragraphs (d)(1) through (9) of this section and § 63.10(e)(3)(vi). This includes periods of startup, shutdown, and malfunction.

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

(2) The date and time that each CMS was inoperative, except for zero (low-level) and high-level checks.

(3) The date, time, and duration that each CMS was out-of-control, including the information in § 63.8(c)(8).

(4) The date and time that each deviation started and stopped, and whether each deviation occurred during a period of startup, shutdown, or malfunction or during another period.

(5) A summary of the total duration of the deviation during the reporting period and the total duration as a percent of the total source operating time during that reporting period.

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

(7) A summary of the total duration of CMS downtime during the reporting period, and the total duration of CMS downtime as a percent of the total source operating time during that reporting period.

(8) A brief description of the process units.

(9) A description of any changes in CMS, processes, or controls since the last reporting period.

(e) Each affected source that has obtained a title V operating permit pursuant to 40 CFR part 70 or 71 must report all deviations as defined in this subpart in the semiannual monitoring report required by 40 CFR 70.6(a)(3)(iii)(A) or 71.6(a)(3)(iii)(A). If an affected source submits a compliance report pursuant to Table 6 to this subpart along with, or as part of, the semiannual monitoring report required by 40 CFR 70.6(a)(3)(iii)(A) or 71.6(a)(3)(iii)(A), and the compliance report includes all required information concerning deviations from any emission limitation in this subpart, submission of the compliance report shall be deemed to satisfy any obligation to report the same deviations in the semiannual monitoring report. However, submission of a compliance report shall not otherwise affect any obligation the affected source may have to report deviations from permit requirements to the permit authority.

(f) For existing sources and for new or reconstructed sources which commenced construction or reconstruction after April 17, 2003, but before February 5, 2019, before October 13, 2020, for each startup, shutdown, or malfunction during the reporting period that is not consistent with your startup, shutdown, and malfunction plan you must submit an immediate startup, shutdown and malfunction report. Unless the Administrator has approved a different schedule for submission of reports under § 63.10(a), you must submit each report according to paragraphs (f)(1) and (2) of this section. An immediate startup, shutdown, and malfunction report is not required after October 13, 2020.

(1) An initial report containing a description of the actions taken for the event must be submitted by fax or telephone within 2 working days after starting actions inconsistent with the plan.

(2) A follow-up report containing the information listed in § 63.10(d)(5)(ii) must be submitted within 7 working days after the end of the event unless you have made alternative reporting arrangements with the permitting authority.

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

(1) Data collected 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 to the EPA via the Compliance and Emissions Data Reporting Interface (CEDRI). CEDRI 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 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. Submit the results of the performance test as an attachment in the ERT.

(3) Confidential business information (CBI). If you claim some of the information submitted under paragraph (g)(1) 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 (g)(1) of this section.

(h) Within 60 days after the date of completing each CMS performance evaluation (as defined in § 63.2), you must submit the results of the performance evaluation following the procedures specified in paragraphs (h)(1) through (3) of this section.

(1) Performance evaluations of CMS measuring relative accuracy test audit (RATA) pollutants that are supported by the EPA's ERT as listed on the EPA's ERT website at the time of the evaluation. Submit the results of the performance evaluation to the EPA via CEDRI, which can be accessed through the EPA's CDX. 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 XML schema listed on the EPA's ERT website.

(2) Performance evaluations of CMS measuring RATA pollutants that are not supported by the EPA's ERT as listed on the EPA's ERT website at the time of the evaluation. Submit the results of the performance evaluation as an attachment in the ERT.

(i) You must submit to the Administrator compliance reports. Beginning on April 16, 2021 or 1 year after the appropriate electronic reporting template becomes available on the CEDRI website, whichever is later, submit all subsequent reports following the procedure specified in paragraph (l) of this section.

(j) You must submit to the Administrator performance evaluations. Beginning on April 16, 2021 or 1 year after the appropriate electronic reporting template becomes available on the CEDRI website, whichever is later, submit all subsequent reports following the procedure specified in paragraph (l) of this section.

(k) You must submit to the Administrator a Notification of Compliance Status. Beginning on April 16, 2021 or 1 year after the appropriate electronic reporting template becomes available on the CEDRI website, whichever is later, submit all subsequent reports following the procedure specified in paragraph (l) of this section.

(l) If you are required to submit reports following the procedure specified in this paragraph, you must submit reports to the EPA via CEDRI. CEDRI 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 date report templates become available will be listed on the CEDRI website. 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.

(m) 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 (m)(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 occurred within the period of time beginning 5 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 caused a delay in reporting.

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

(i) The date, time and length of the outage;

(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.

(n) 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 majeure, you must meet the requirements outlined in paragraphs (n)(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 5 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 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 19090, Apr. 17, 2003, as amended at 71 FR 17745, Apr. 7, 2006; 85 FR 20868, Apr. 15, 2020]