WELL · 42-041-30818 · DISTRICT 3
Chatham Unit #1
Brazos County · Bryan N. (Georgetown) field · Vertical
Chatham Unit #1 (API 42-041-30818) is a plugged well in Brazos County, plugged April 20, 2000, last operated by Andrus Resources Corporation.
The RRC has issued one drilling permit, issued September 20, 1982, permitted to 9,250 ft.
It was permitted by Mcz, Inc. and has since transferred to Andrus Resources Corporation on the wellbore schedule.
Its lease has reported 1.32M barrels of oil and 2.3M mcf of gas since January 1993, last reporting in July 2026. The lease carries 114 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by MCZ, Inc.; the EWA schedule now lists a different operator.
Houston, TX · P-5 Y, filed Apr 4, 2003 · 8 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Andrus Resources Corporation |
| Production reports | B.W.O.C., Inc.through Jun 2002 |
| Latest permit | MCZ, Inc.Sep 20, 1982 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,250
- total depth, ft
- 1
- permits on file
- Sep 20, 1982
- last permit issued
- Nov 1, 1982
- completed
- 1.32M
- cumulative oil, bbl
- 2.3M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 1, 1982
- Shut in
- —
- Plugged
- Apr 20, 2000
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 114 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Bryan Woodbine Unit O-3-18630 | Bryan (Woodbine) | B.W.O.C., Inc. | 114 | 1.32M | 2.3M | Jan 1993 – Jul 2026 |
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.
- 1B.W.O.C., Inc.Jan 1993 → Jun 2002
Permits
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-3-18630 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,268 | 8,278 | Perforated |
| 8,898 | 9,014 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,690 | 13.75 | 930 S |
| 5.5 | 9,100 | 8.75 | 2,575 S |
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 | Jul 18, 1985 | Nov 16, 1982 | — |
| 00 | Jul 13, 1985 | — | — |
| 00 | Jan 12, 1984 | Nov 16, 1982 | — |
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-041-30818 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-041-30818 → 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.
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/04130818, documented in the API reference.