WELL · 42-363-34537 · DISTRICT 7
Johnson A #1
Palo Pinto County · Palo Pinto County Regular field · Vertical
Johnson A #1 (API 42-363-34537) is a plugged well in Palo Pinto County, plugged August 15, 2019, last operated by Pitcock Inc..
The RRC has issued one drilling permit, issued March 25, 1996, permitted to 1,750 ft.
It was permitted by Talon Production, Inc. and has since transferred to Pitcock Inc. on the wellbore schedule.
Completion filings report 3 formation tops, including Lime, Canyon, Strawn.
Operator of record
Permitted by Talon Production, Inc.; the EWA schedule now lists a different operator.
Graham, TX · P-5 Y, filed Jun 4, 2026 · 265 permits on file · (940) 550-5255
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Pitcock Inc. |
| Production reports | Pitcock, Inc.through Apr 2018 |
| Latest permit | Talon Production, Inc.Mar 25, 1996 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 1,750
- total depth, ft
- 1
- permits on file
- Mar 25, 1996
- last permit issued
- Jun 10, 1996
- completed
- 0
- cumulative oil, bbl
- 102K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 1996 THROUGH Aug 2019
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 10, 1996
- Shut in
- —
- Plugged
- Aug 15, 2019
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 |
|---|---|---|---|---|---|---|
| Johnson A G-8-158857 | Palo Pinto County Regular | Pitcock, Inc. | 1 | 0 | 102K | Jun 1996 – Aug 2019 |
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.
- 1Talon Production, Inc.Jun 1996 → Dec 1996
- 2Pitcock, Inc.Mar 1997 → Apr 2018
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 446127-99 | Drill | Talon Production, Inc. | Mar 21, 1996 | Mar 25, 1996 | Apr 22, 1996 | 1,750 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-158857 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,223 | 1,242 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,270 | 6.75 | 150 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 26, 1996 | Jul 5, 1996 | Yes |
| 00 | Jul 12, 1996 | — | — |
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-363-34537 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-363-34537 → 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/36334537, documented in the API reference.