WELL · 42-251-32557 · DISTRICT 9
Lanham #1H
Johnson County · Newark East (Barnett Shale) field · Horizontal
Lanham #1H (API 42-251-32557) is a plugged horizontal well in Johnson County, plugged December 20, 2010, last operated by Arrington David H. Oil & Gas Inc.
The RRC has issued one drilling permit, issued January 25, 2008, permitted to 8,500 ft.
Completion filings report 4 formation tops, including Base Cretaceous (marker), Marble Falls, Barnett, Ellenburger.
Operator of record
Arrington David H. Oil & Gas Inc
Midland, TX · P-5 Y, filed Jul 2, 2015 · 252 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Arrington David H. Oil & Gas Inc |
| Production reports | none |
| Latest permit | Arrington,david H. Oil & Gas,incJan 25, 2008 |
- 8,500
- total depth, ft
- 1
- permits on file
- Jan 25, 2008
- last permit issued
- Feb 22, 2008
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Feb 2008 THROUGH Dec 2010
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Feb 22, 2008
- Shut in
- —
- Plugged
- Dec 20, 2010
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 |
|---|---|---|---|---|---|---|
| Lanham G-13-248093 | Newark, East (Barnett Shale) | Arrington,david H. Oil & Gas,inc | 1 | 0 | 0 | Feb 2008 – Dec 2010 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 653546-99 | Drill | Arrington,david H. Oil & Gas,inc | Jan 18, 2008 | Jan 25, 2008 | Jan 30, 2008 | 8,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-248093 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 795 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Base Cretaceous (marker)BASE CRETACEOUS | 1,442 | -647 |
| Marble Falls | 7,282 | -6,487 |
| BarnettBARNETT SHALE | 7,712 | -6,917 |
| Ellenburger | 8,066 | -7,271 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,436 | 8,114 | Perforated |
| 8,856 | 8,535 | Perforated |
| 9,274 | 8,954 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,615 | 12.25 | 500 S |
| 5.5 | 9,381 | 8.75 | 840 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 13, 2009 | Jul 11, 2008 | Yes |
| 00 | Jun 15, 2009 | — | — |
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-251-32557 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-251-32557 → 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/25132557, documented in the API reference.