WELL · 42-263-31977 · DISTRICT 8

Morrison J. W. #4

N

Kent County · Lyn-Kay (6200) field  · Vertical

Morrison J. W. #4 (API 42-263-31977) is a well in Kent County operated by Brown Geo. R Partnership LP The, completed January 12, 2012.

The RRC has issued one drilling permit, issued September 20, 2011, permitted to 6,500 ft.

Completion filings report 3 formation tops, including Glorieta, Valera, Sms Sand.

Its 2 leases have reported 150K barrels of oil and 43.4K mcf of gas since January 1993, last reporting in July 2026. The leases carry 5 wells, so these are lease totals, not this well alone.

Operator of record

Brown Geo. R Partnership LP The

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 3, 2026
Permits on file
160
Phone
(713) 652-4901

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBrown Geo. R Partnership LP The
Production reportsBrown, Geo. R Partnership,lp,thethrough Apr 2026
Latest permitBrown, Geo. R Partnership,lp,theSep 20, 2011
6,500
total depth, ft
1
permits on file
Sep 20, 2011
last permit issued
Jan 12, 2012
completed
150K
cumulative oil, bbl
43.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 12, 2012
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 2 leases this well is completed on; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Morrison, J. W. O-11-61687Lyn-Kay (6200)Brown, Geo. R Partnership,lp,the4126K33.1KJan 1993 – Jul 2026
Morrison, J. W. "A" O-11-69907Lyn-Kay (6200)Brown, Geo. R Partnership,lp,the123.9K10.3KJan 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 1,867 · prior 12 1,641(+14%)

0100200300202420252026

Gas, mcf lease total

Last 12 months 720 · prior 12 1,800(-60%)

0100200202420252026

Chain of custody

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

  1. 1Brown, George R. Partnership,theJan 1993 → Apr 2003
  2. 2Brown, Geo. R Partnership,lp,theMay 2003 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
724028-99DrillBrown, Geo. R Partnership,lp,theSep 12, 2011Sep 20, 2011Oct 24, 20116,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-61687————
—— O-11-69907————

Formation tops

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

FormationMD ftSubsea
Glorieta2,16036
Valera3,806-1,610
SMS Sand6,140-3,944

Perforations

Perforated and open-hole intervals.

FromToType
6,1426,172Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,61312.251,000 S
5.56,2797.875315 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
00Jan 22, 2013Feb 20, 2012Yes
00Aug 31, 2012Feb 20, 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.

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