WELL · 42-195-00200 · DISTRICT 10
Collier, H. J. #E 2
Hansford County · Vertical
Collier, H. J. #E 2 (API 42-195-00200) is a former disposal or injection well in Hansford County, last operated by Exxon Mobil Corporation; its UIC permit is no longer active.
The RRC has issued one drilling permit, issued August 12, 2002, permitted to 4,656 ft.
Its lease has reported 6.29K barrels of oil and 34.4K mcf of gas since January 1993, last reporting in February 2011. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Spring, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jul 15, 2026
- Permits on file
- 1,223
- Phone
- (346) 474-9142
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Exxon Mobil Corporationthrough Jun 2003 |
| Latest permit | Exxon Mobil CorporationAug 12, 2002 |
- 4,656
- total depth, ft
- 1
- permits on file
- Aug 12, 2002
- last permit issued
- —
- completed
- 6.29K
- cumulative oil, bbl
- 34.4K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2011
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Collier, HJ -E- O-14-22 | Hitchland (4640) | Exxon Mobil Corporation | 2 | 6.29K | 34.4K | Jan 1993 – Feb 2011 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Exxon Corp.Jan 1993 → Mar 2000
- 2Exxon Mobil CorporationApr 2000 → Jun 2003
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 522633-99 | Recompletion | Exxon Mobil Corporation | Aug 7, 2002 | Aug 12, 2002 | — | 4,656 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-14-22 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| — | 4,632 | Perforated |
Completion filings
W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | — | — |
The source documents
Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.
- Wellbore filings for 42-195-00200 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-195-00200 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- —
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000092444 | W-14 Disposal | Plugged Dec 29, 2009 | 650 | 500 | 1,050–1,150 |
About this data
Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.
New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease
Developers: this page as JSON is GET /v1/data/wells/19500200, documented in the API reference.