TEXAS · WELLS · LIPSCOMB COUNTY · LIPSCOMB -796- LEASE · API 42-295-31364 · DISTRICT 08

Lipscomb -796- #1

Plugged

Lipscomb County · Trenfield (Cleveland) field  · Vertical

Lipscomb -796- #1 (API 42-295-31364) is a plugged well in Lipscomb County, plugged December 28, 1995, last operated by Mewbourne Oil Company.

The RRC has issued one drilling permit, issued August 4, 1983, permitted to 9,000 ft.

Completion filings report 7 formation tops, including Brown Dolomite, Pennsylvanian, Base Of Heebner, Douglas.

Its lease has reported 750 barrels of oil and 18.1K mcf of gas since January 1993, with no volume in the three years through April 2026.

Operator of record

Mewbourne Oil Company

Based in
Tyler, TX
P-5 status
Active (A)
P-5 last filed
May 21, 2026
Permits on file
2,061
Phone
(903) 561-2900

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMewbourne Oil Company
Production reportsMewbourne Oil Companythrough Dec 1995
Latest permitMewbourne Oil Co.Aug 4, 1983
9,000
total depth, ft
1
permits on file
Aug 4, 1983
last permit issued
Oct 30, 1983
completed
750
cumulative oil, bbl
18.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 30, 1983
Shut in
—
Plugged
Dec 28, 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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lipscomb -796- G-14-111670Trenfield (Cleveland)Mewbourne Oil Company175018.1KJan 1993 – Dec 1995

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.

  1. 1Mewbourne Oil CompanyJan 1993 → Dec 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
204220-99DrillMewbourne Oil Co.Jul 19, 1984Aug 4, 1983Oct 28, 19839,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 30, 1983Lipscomb -796- G-14-111670Trenfield (Cleveland)Mewbourne Oil CompanyPlugged—

Formation tops

As filed on W-2/G-1. Subsea from 2,420 ft elevation.Download CSV →

FormationMD ftSubsea
Brown Dolomite3,460-1,040
PennsylvanianPENN SHALE5,050-2,630
Base of Heebner6,098-3,678
Douglas6,152-3,732
Tonkawa6,592-4,172
Cleveland7,613-5,193
Hepler7,777-5,357

Perforations

Perforated and open-hole intervals.

FromToType
7,6517,667Perforated
7,6707,676Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,83512.251,200 sx
4.57,9007.875375 sx

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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Aug 6, 1984Jul 19, 1984—
00Aug 4, 1984Jul 19, 1984—

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.

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/29531364, documented in the API reference.