WELL · 42-503-40265 · DISTRICT 9
Cloud Ranch #3
Young County · Young County Regular (Gas) field · Vertical
Cloud Ranch #3 (API 42-503-40265) is a plugged well in Young County, plugged August 10, 1995, last operated by Petroil Development Corporation.
The RRC has issued one drilling permit (amended once), issued November 28, 1990, permitted to 4,999 ft.
Completion filings report 3 formation tops, including Caddo, Upper Conglomerate, Mississippian.
Operator of record
Petroil Development Corporation
Plano, TX · P-5 Y, filed Dec 4, 2025 · 9 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Petroil Development Corporation |
| Production reports | none |
| Latest permit | Petroil Development CorporationNov 28, 1990 |
- 4,999
- total depth, ft
- 2
- permits on file
- Nov 28, 1990
- last permit issued
- Mar 5, 1991
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 5, 1991
- Shut in
- —
- Plugged
- Aug 10, 1995
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 |
|---|---|---|---|---|---|---|
| Cloud Ranch G-13-138888 | Young County Regular (Gas) | Petroil Development Corporation | 1 | 0 | 0 | Jan 1993 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 381642-98 | Drill | Petroil Development Corporation | May 29, 1991 | Nov 28, 1990 | Nov 30, 1990 | 4,999 |
| 381642-99 | Drill | Petroil Development Corporation | Nov 28, 1990 | Nov 28, 1990 | — | 4,999 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-138888 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,201 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| CaddoUPPER CADDO | 3,534 | -2,333 |
| CaddoLOWER CADDO | 3,807 | -2,606 |
| Upper Conglomerate | 4,235 | -3,034 |
| Mississippian | 4,606 | -3,405 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,235 | 4,242 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 167 | 12.25 | 105 S |
| 5.5 | 4,555 | 7.875 | 236 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 | Aug 21, 1991 | May 20, 1991 | Yes |
| 00 | Aug 8, 1991 | — | — |
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-503-40265 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-503-40265 → 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/50340265, documented in the API reference.