TEXAS · WELLS · CALDWELL COUNTY · KELLY, J.J. -B- LEASE · API 42-055-31650 · DISTRICT 01

Kelly J.J. -B- #10

N

Caldwell County · Luling-Branyon field  · Vertical

Kelly J.J. -B- #10 (API 42-055-31650) is a well in Caldwell County operated by Great Plains Resources Inc., completed December 10, 1980.

The RRC has issued one drilling permit, issued November 18, 1980, permitted to 2,750 ft.

It was permitted by Lpg Energy Partnership and has since transferred to Great Plains Resources Inc. on the wellbore schedule.

Its lease has reported 105 barrels of oil since January 1993, with no volume in the three years through April 2026.

Operator of record

Great Plains Resources Inc.

Permitted by LPG Energy Partnership; the EWA schedule now lists a different operator.

Based in
Nixon, TX
P-5 status
Delinquent (D)
P-5 last filed
Sep 3, 1997
Phone
(210) 582-2588

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGreat Plains Resources Inc.
Production reportsGreat Plains Resources, Inc.through Jun 1998
Latest permitLPG Energy PartnershipNov 18, 1980

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

2,750
total depth, ft
1
permits on file
Nov 18, 1980
last permit issued
Dec 10, 1980
completed
105
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1994 THROUGH Jun 1998

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 10, 1980
Shut in
—
Plugged
—

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
Kelly, J.J. -B- O-1-6860Luling-BranyonGreat Plains Resources, Inc.11050Jan 1993 – Jun 1998

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. 1Rao Oil CompanyOct 1994 → Oct 1994
  2. 2Ginco Operating Co.Mar 1995 → Oct 1995
  3. 3Great Plains Resources, Inc.Jan 1997 → Jun 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
99636-99DrillLPG Energy PartnershipNov 18, 1980Nov 18, 1980—2,750

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 10, 1980Kelly J.J. -B- O-1-6860Luling-BranyonGreat Plains Resources Inc.Not on Schedule—

Perforations

Perforated and open-hole intervals.

FromToType
2,0422,200Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62515012.5165 S
22,030——
5.52,3317.875330 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
00Jan 12, 1984Apr 20, 1981—

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