WELL · 42-479-30622 · DISTRICT 4
Williamson #1
Webb County · Las Pintas East (Lobo) field · Vertical
Williamson #1 (API 42-479-30622) is a plugged well in Webb County, plugged August 28, 2006, last operated by Tidal Petroleum Inc..
The RRC has issued 2 drilling permits between 1978 and 2005, permitted to 8,200 ft.
Operator of record
Schertz, TX · P-5 Y, filed Apr 4, 2026 · 256 permits on file · (361) 362-4668
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Tidal Petroleum Inc. |
| Production reports | Tidal Petroleum, Inc.through Jul 2006 |
| Latest permit | Tidal Petroleum, Inc.Sep 19, 2005 |
- 8,200
- total depth, ft
- 2
- permits on file
- Sep 19, 2005
- last permit issued
- Oct 13, 2005
- completed
- 0
- cumulative oil, bbl
- 18.3K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2006
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 13, 2005
- Shut in
- —
- Plugged
- Aug 28, 2006
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 |
|---|---|---|---|---|---|---|
| Williamson G-4-216060 | Las Pintas, East (Lobo) | Tidal Petroleum, Inc. | 1 | 0 | 12.1K | Oct 2005 – Aug 2006 |
| Williams & Williamson G-4-78552 | Las Pintas (Hirsch Sd.) | Lewis Petro Properties, Inc. | 1 | 0 | 6.18K | Jan 1993 – May 1994 |
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.
- 1Lewis Petro Properties, Inc.Jan 1993 → Mar 1994
- 2Tidal Petroleum, Inc.Dec 2005 → Jul 2006
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 606478-99 | Reenter | Tidal Petroleum, Inc. | Sep 16, 2005 | Sep 19, 2005 | Oct 7, 2005 | 8,012 |
| 24405-99 | Other | Guardian Oil Company | May 16, 1978 | May 16, 1978 | — | 8,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-78552 | — | — | — | — |
| — | — G-4-216060 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,697 | 7,709 | Perforated |
| 7,759 | 7,769 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 400 | — | — |
| 4.5 | 7,914 | 7.875 | 1,290 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 | Sep 20, 2006 | Feb 7, 2006 | Yes |
| 00 | May 26, 2006 | — | — |
| 00 | Jan 12, 1984 | Sep 27, 1978 | — |
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-479-30622 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-479-30622 → 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/47930622, documented in the API reference.