WELL · 42-503-39790 · DISTRICT 9
Chappel #1
Young County · Young County Regular field · Vertical
Chappel #1 (API 42-503-39790) is a plugged well in Young County, plugged October 1, 1991, last operated by Palmer Tank Trucks Inc..
The RRC has issued one drilling permit, issued May 10, 1988, permitted to 4,999 ft.
It was permitted by Ingram, J. Oil & Gas Inc. and has since transferred to Palmer Tank Trucks Inc. on the wellbore schedule.
Completion filings report 3 formation tops, including Caddo, Marble Falls, Barnett.
Operator of record
Permitted by Ingram, J. Oil & Gas Inc.; the EWA schedule now lists a different operator.
Olney, TX · P-5 Y, filed Jun 6, 2008 · 15 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Palmer Tank Trucks Inc. |
| Production reports | none |
| Latest permit | Ingram, J. Oil & Gas Inc.May 10, 1988 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 4,999
- total depth, ft
- 1
- permits on file
- May 10, 1988
- last permit issued
- May 27, 1988
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 27, 1988
- Shut in
- —
- Plugged
- Oct 1, 1991
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 |
|---|---|---|---|---|---|---|
| — O-13-27081 | — | — | 0 | 0 | 0 | — |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 346384-99 | Drill | Ingram, J. Oil & Gas Inc. | May 10, 1988 | May 10, 1988 | — | 4,999 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-27081 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,150 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Caddo | 4,230 | -3,080 |
| Marble FallsMARBLE FALLS LIME | 4,528 | -3,378 |
| BarnettBARNETT SHALE | 4,715 | -3,565 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,785 | 4,799 | Open hole |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 161 | 12.25 | 115 S |
| 4.5 | 4,785 | 7.875 | 125 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 11, 1988 | Jun 24, 1988 | Yes |
| 00 | Jun 30, 1988 | — | — |
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-39790 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-503-39790 → 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/50339790, documented in the API reference.