TEXAS · WELLS · LIMESTONE COUNTY · API 42-293-31024 · DISTRICT 05
Hudson A #2
Limestone County · Freestone (CV-Bossier Cons.) field · Temp Abandoned · Vertical
Hudson A #2 (API 42-293-31024) is a well in Limestone County operated by Hilcorp Energy Company, completed December 23, 1993 and listed as temp abandoned on the RRC schedule, shut in January 1, 1998.
The RRC has issued one drilling permit, issued September 28, 1993, permitted to 11,850 ft.
It was permitted by Marathon Oil Company and has since transferred to Hilcorp Energy Company on the wellbore schedule.
Completion filings report 7 formation tops, including Austin Chalk, Buda, Glen Rose, Mass. Anhyd..
Its 2 leases have reported 8.22K barrels of oil and 2.17M mcf of gas since December 1993, with no volume in the three years through April 2026. The leases carry 2 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Marathon Oil Company; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 27, 2026
- Permits on file
- 3,458
- Phone
- (713) 209-2400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Hilcorp Energy Company |
| Production reports | Hilcorp Energy Companythrough Jun 1997 |
| Latest permit | Marathon Oil CompanySep 28, 1993 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 11,850
- total depth, ft
- 1
- permits on file
- Sep 28, 1993
- last permit issued
- Dec 23, 1993
- completed
- 8.22K
- cumulative oil, bbl
- 2.17M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1994 THROUGH Jun 1997
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 23, 1993
- Shut in
- Jan 1, 1998
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 2 leases 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 |
|---|---|---|---|---|---|---|
| Hudson "A" G-5-148703 | Freestone (CV-Bossier Cons.) | Hilcorp Energy Company | 1 | 6.19K | 1.96M | Dec 1993 – Jun 1997 |
| Hudson "A" G-5-150487 | Pine Oak Creek, N. (Bossier) | Marathon Oil Company | 1 | 2.03K | 208K | May 1994 – Oct 1995 |
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.
- 1Marathon Oil CompanyJan 1994 → Jun 1997
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 416519-99 | Drill | Marathon Oil Company | Sep 28, 1993 | Sep 28, 1993 | Oct 2, 1993 | 12,350 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Dec 23, 1993 | Hudson A G-5-148703 | Freestone (CV-Bossier Cons.) | Hilcorp Energy Company | Temp Abandoned · shut in Jan 1, 1998 | 11,850 |
| May 26, 1994 | Hudson A G-5-150487 | Pine Oak Creek N. (Bossier) | Marathon Oil Company | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 439 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin ChalkBASE AUSTIN CHALK | 4,092 | -3,653 |
| Buda | 4,895 | -4,456 |
| Glen Rose | 6,185 | -5,746 |
| Mass. Anhyd. | 7,260 | -6,821 |
| Pettit | 7,953 | -7,514 |
| Travis Peak | 8,170 | -7,731 |
| Bossier | 10,870 | -10,431 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,356 | 8,370 | Perforated |
| 8,356 | 8,880 | Perforated |
| 8,440 | 8,460 | Perforated |
| 8,776 | 8,788 | Perforated |
| 8,852 | 8,880 | Perforated |
| 11,091 | 11,158 | Perforated |
| 11,091 | 11,509 | Perforated |
| 11,216 | 11,249 | Perforated |
| 11,286 | 11,304 | Perforated |
| 11,442 | 11,456 | Perforated |
| 11,482 | 11,509 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,555 | 12.25 | 565 S |
| 9.625 | 1,565 | 12.25 | 565 S |
| 4.5 | 11,850 | 7.875 | 2,283 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Apr 15, 1996 | Jan 29, 1996 | — |
| 00 | Sep 8, 1994 | Jun 24, 1994 | Yes |
| 00 | Aug 24, 1994 | — | — |
| 00 | Apr 20, 1994 | Feb 7, 1994 | Yes |
| 00 | Apr 12, 1994 | — | — |
Well logs
The RRC's map lists this well among those with logs online. Its monthly inventories loaded here, which start in July 2006, list none for it, so none are itemized.
Open the RRC's log search for this well ↗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-293-31024 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-293-31024 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/29331024, documented in the API reference.