WELL · 42-181-31497 · DISTRICT 9

Melton A #2

Y

Grayson County · Sherman East (Penn. 7100) field · Shut IN  · Directional

Melton A #2 (API 42-181-31497) is a well in Grayson County operated by Longfellow Energy LP, completed October 26, 2018 and listed as shut in on the RRC schedule.

The RRC has issued 2 drilling permits (amended once) between 2012 and 2018, permitted to 13,000 ft.

Completion filings report 13 formation tops, including Baker, Baker Sand, Davis, Davis Sand.

Its 2 leases have reported 7.35K barrels of oil and 21.3K mcf of gas since June 2012, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Longfellow Energy LP

Dallas, TX · P-5 Y, filed Dec 4, 2025 · 37 permits on file · (405) 306-6169

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLongfellow Energy LP
Production reportsLongfellow Energy, LPthrough Sep 2021
Latest permitLongfellow Energy, LPDec 4, 2018
13,000
total depth, ft
3
permits on file
Dec 4, 2018
last permit issued
Oct 26, 2018
completed
7.35K
cumulative oil, bbl
21.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 26, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

33.666892, -96.572964

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Grayson County.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Melton A O-13-32348Denison, S. (Woodlake)Longfellow Energy, LP14.68K12.2KJun 2012 – Jul 2026
Melton A O-13-33865Sherman, East (Penn. 7100)Longfellow Energy, LP12.67K9.17KOct 2018 – Jul 2026

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. 1Longfellow Energy, LPJun 2012 → Sep 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
847190-99RecompletionLongfellow Energy, LPNov 27, 2018Dec 4, 2018—11,205
736708-98DrillLongfellow Energy, LPSep 13, 2012Apr 5, 2012Apr 14, 201213,000
736708-99DrillLongfellow Energy, LPMar 23, 2012Apr 5, 2012Apr 13, 201213,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-32348————
—— O-13-33865————

Formation tops

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

FormationMD ftSubsea
Baker8,161-7,400
Baker Sand8,164-7,403
Davis8,931-8,170
Davis Sand8,940-8,179
Woodlake9,606-8,845
Barnes Sand——
Bruhlmeyer——
Carraway Sand——
Covey——
Handy Sand——
Huff Sand——
Paluxy——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
8,2358,392Perforated
8,23510,449Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,36412.25530 S
5.511,3557.875850 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
00May 2, 2019Mar 14, 2019—
00Feb 27, 2013Nov 7, 2012Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Skaggs42-181-31481

1.1 KM · Longfellow Energy, LP · Section with this well →

Baker8,151-7,397
Davis8,905-8,151
Woodlake9,818-9,064
Simpson10,629-9,875
Viola10,660-9,906

Brown, A.C. Unit42-181-31080

10.9 KM · Younger Energy Company · Section with this well →

Grey Deece6,676-5,948
Baker7,925-7,197
Davis8,755-8,027
Lester Lime9,152-8,424
Cordell9,650-8,922

Hudgins42-181-31601

11.3 KM · Kornye-Tillman Company · Section with this well →

Paluxy898-167
Strawn5,928-5,197
Baker Sand6,842-6,111
Davis Sand7,892-7,161
Handy Sand—
Bruhlmeyer—
Huff Sand—
Barnes Sand—

10 TOPS · FIRST 8

Lee42-181-31024

12.0 KM · Younger Energy Company · Section with this well →

V Sand6,780-6,047
Baker6,800-6,067
Davis7,778-7,045
Cordell8,845-8,112
Pennsylvanian9,665-8,932
Pennsylvanian9,665-8,932
Pennsylvanian9,665-8,932

Bickenbach42-181-31649

12.5 KM · Atoka Energy LLC · Section with this well →

Strawn—
Baker Sand—
Barnes Sand—
Bruhlmeyer—
Carraway Sand—
Covey—
Davis Sand—
Handy Sand—

10 TOPS · FIRST 8

Withrow (V)42-181-31527

12.5 KM · Jetta Operating Company, Inc. · Section with this well →

Baker7,648-6,934
Base of Baker8,544-7,830
Lower Dornick Hills8,632-7,918
Davis9,045-8,331
U Davis9,048-8,334
Lower Davis9,210-8,496
Cordell9,435-8,721
Viola9,854-9,140

East McDaniels42-181-31600

12.6 KM · Atoka Operating, Inc. · Section with this well →

Davis Sand9,410-8,700
Bruhlmeyer—
Carraway Sand—
Covey—
Handy Sand—
Huff Sand—
Paluxy—
Strawn—

10 TOPS · FIRST 8

Slagle-Fallon A42-181-31267

13.2 KM · Little, Quintin Company,inc.,the · Section with this well →

Strawn2,415-1,589
Bruhlmeyer2,890-2,064
Baker Sand7,421-6,595
Davis Sand7,650-6,824
Huff Sand—
Paluxy—
Barnes Sand—
Carraway Sand—

10 TOPS · FIRST 8

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