TEXAS · WELLS · LIPSCOMB COUNTY · KOCH LITTLE '779' LEASE · API 42-295-33907 · DISTRICT 08

Koch Little 779 #1H

Y

Lipscomb County · Lipscomb (Cleveland) field · Producing  · Horizontal

Koch Little 779 #1H (API 42-295-33907) is a horizontal well in Lipscomb County operated by Mewbourne Oil Company, completed December 24, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 27, 2012, permitted to 7,809 ft.

Completion filings report 3 formation tops, including Pennsylvanian, Heebner Shale, Cleveland.

Its lease has reported 46.7K barrels of oil and 873K mcf of gas since December 2012, last reporting volume in 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 Apr 2026
Latest permitMewbourne Oil CompanyAug 27, 2012
7,809
total depth, ft
1
permits on file
Aug 27, 2012
last permit issued
Dec 24, 2012
completed
46.7K
cumulative oil, bbl
873K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2012 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 24, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Koch Little '779' G-14-270438Lipscomb (Cleveland)Mewbourne Oil Company146.7K873KDec 2012 – Apr 2026

Gas, mcf lease total

Last 12 months 26,853 · prior 12 23,563(+14%)

01K2K3K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Mewbourne Oil CompanyDec 2012 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
746723-99DrillMewbourne Oil CompanyAug 20, 2012Aug 27, 2012Oct 28, 20128,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 24, 2012Koch Little 779 G-14-270438Lipscomb (Cleveland)Mewbourne Oil CompanyProducing7,809

Formation tops

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

FormationMD ftSubsea
PennsylvanianPENN SHALE5,064-2,502
Heebner Shale6,143-3,581
Cleveland7,746-5,184

Perforations

Perforated and open-hole intervals.

FromToType
8,19011,971Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,02312.25775 S
78,1448.7550 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. 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
00Oct 29, 2013Jan 14, 2013Yes

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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