TEXAS · WELLS · KARNES COUNTY · FRANKE-JOHNSON UNIT LEASE · API 42-255-35191 · DISTRICT 02

Franke-Johnson Unit #16H

Y

Karnes County · Sugarkane (Eagle Ford) field · Producing  · Horizontal

Franke-Johnson Unit #16H (API 42-255-35191) is a horizontal well in Karnes County operated by Marathon Oil EF LLC, completed May 21, 2018 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 12, 2016, permitted to 12,550 ft.

Completion filings report 10 formation tops, including Yegua, Queen City, Reklaw, Carrizo.

No lease production has been reported under this well’s leases.

Operator of record

Marathon Oil EF LLC

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Sep 26, 2025
Permits on file
3,191
Phone
(832) 486-2737

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMarathon Oil EF LLC
Production reportsMarathon Oil EF LLCthrough Apr 2026
Latest permitMarathon Oil EF LLCDec 12, 2016
12,550
total depth, ft
1
permits on file
Dec 12, 2016
last permit issued
May 21, 2018
completed
0
cumulative oil, bbl
1.93M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 21, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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
Franke-Johnson Unit G-2-284179Sugarkane (Eagle Ford)Marathon Oil EF LLC101.93MMar 2017 – Jul 2026

Gas, mcf lease total

Last 12 months 126,188 · prior 12 161,912(-22%)

010K20K30K202420252026

Chain of custody

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

  1. 1Marathon Oil EF LLCMay 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
820377-99DrillMarathon Oil EF LLCNov 15, 2016Dec 12, 2016Apr 25, 201819,500

Completions

CompletedLeaseFieldOperatorStatusDepth
May 21, 2018Franke-Johnson Unit G-2-284179Sugarkane (Eagle Ford)Marathon Oil EF LLCProducing12,550

Formation tops

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

FormationMD ftSubsea
YeguaYEGUA - DISPOSAL2,040-1,627
Queen City4,372-3,959
Reklaw4,835-4,422
Carrizo5,339-4,926
WilcoxWILCOX - DISPOSAL6,663-6,250
Austin ChalkAUSTIN CHALK - H2S12,139-11,726
Eagle FordEAGLE FORD - H2S12,288-11,875
EdwardsEDWARDS - H2S——
FrioFRIO - DISPOSAL——
SligoSLIGO - H2S——

Perforations

Perforated and open-hole intervals.

FromToType
12,42818,466Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6255,75012.251,533 S
5.518,5758.753,265 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Oct 24, 2018Jun 15, 2018Yes
00Jun 26, 2018Mar 15, 2018Yes

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