TEXAS · WELLS · LIVE OAK COUNTY · MASSEY BALDWIN LEASE · API 42-297-35348 · DISTRICT 02

Massey Baldwin #3H

Y

Live Oak County · Eagleville (Eagle Ford-2) field · Producing  · Horizontal

Massey Baldwin #3H (API 42-297-35348) is a horizontal well in Live Oak County operated by Marathon Oil EF LLC, completed July 25, 2014 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 2, 2013, permitted to 11,692 ft.

Completion filings report 3 formation tops, including Anacacho, Austin Chalk, Eagle Ford.

Its lease has reported 586K barrels of oil and 1.42M mcf of gas since August 2013, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

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 Nov 2025
Latest permitMarathon Oil EF LLCApr 2, 2013
11,692
total depth, ft
1
permits on file
Apr 2, 2013
last permit issued
Jul 25, 2014
completed
586K
cumulative oil, bbl
1.42M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 25, 2014
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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Massey Baldwin O-2-10630Eagleville (Eagle Ford-2)Marathon Oil EF LLC3586K1.42MAug 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 3,024 · prior 12 9,631(-69%)

05001K202420252026

Gas, mcf lease total

Last 12 months 6,820 · prior 12 24,238(-72%)

02K4K202420252026

Chain of custody

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

  1. 1Marathon Oil EF LLCAug 2013 → Nov 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
759725-99DrillMarathon Oil EF LLCMar 28, 2013Apr 2, 2013Aug 1, 201316,700

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 25, 2014Massey Baldwin O-2-10630Eagleville (Eagle Ford-2)Marathon Oil EF LLCProducing11,692

Formation tops

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

FormationMD ftSubsea
Anacacho11,029-10,787
Austin Chalk11,285-11,043
Eagle Ford11,352-11,110

Perforations

Perforated and open-hole intervals.

FromToType
11,56716,417Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6255,84112.251,665 S
5.516,5538.51,725 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 12, 2016Oct 10, 2016—
00Nov 7, 2013Sep 9, 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 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/29735348, documented in the API reference.