WELL · 42-441-33907 · DISTRICT 7
Ledbetter Ranch #3
Taylor County · Ledbetter Ranch (Cook Sd.) field · Vertical
Ledbetter Ranch #3 (API 42-441-33907) is a plugged well in Taylor County, plugged December 20, 2002, last operated by Guffey WM. R..
The RRC has issued one drilling permit, issued April 22, 1999, permitted to 3,300 ft.
Completion filings report 3 formation tops, including Saddle Creek, Flippen, Cook Sand.
Its lease has reported 372 barrels of oil and 1.36K mcf of gas since May 1999, last reporting in February 2003.
Operator of record
Dallas, TX · P-5 Y, filed Aug 7, 2015 · 68 permits on file · (214) 522-9429
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Guffey Wm. R. |
| Production reports | Guffey, Wm. R.through Sep 1999 |
| Latest permit | Guffey, Wm. R.Apr 22, 1999 |
- 3,300
- total depth, ft
- 1
- permits on file
- Apr 22, 1999
- last permit issued
- May 28, 1999
- completed
- 372
- cumulative oil, bbl
- 1.36K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 1999 THROUGH Feb 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 28, 1999
- Shut in
- —
- Plugged
- Dec 20, 2002
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Ledbetter Ranch O-8-28616 | Ledbetter Ranch (Cook Sd.) | Guffey, Wm. R. | 1 | 372 | 1.36K | May 1999 – Feb 2003 |
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.
- 1Guffey, Wm. R.May 1999 → Sep 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 483887-99 | Drill | Guffey, Wm. R. | Apr 15, 1999 | Apr 22, 1999 | Apr 24, 1999 | 3,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-28616 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,367 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Saddle Creek | 2,964 | -597 |
| Flippen | 3,003 | -636 |
| Cook Sand | 3,061 | -694 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,061 | 3,066 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 271 | 12.25 | 160 S |
| 5.5 | 3,295 | 7.875 | 265 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 29, 1999 | Jun 11, 1999 | Yes |
| 00 | Jun 30, 1999 | — | — |
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-441-33907 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-441-33907 → 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/44133907, documented in the API reference.