WELL · 42-393-30644 · DISTRICT 10
The Mother Bear #2
Roberts County · Shreikey (Morrow) field · Vertical
The Mother Bear #2 (API 42-393-30644) is a plugged well in Roberts County, plugged September 24, 1990, last operated by Chevron U. S. A. Inc..
The RRC has issued 4 drilling permits between 1978 and 2008, permitted to 11,300 ft.
It was permitted by Cimarex Energy CO. Of Colorado and has since transferred to Chevron U. S. A. Inc. on the wellbore schedule.
Operator of record
Permitted by Cimarex Energy Co. of Colorado; the EWA schedule now lists a different operator.
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jan 30, 2026
- Permits on file
- 9,293
- Phone
- (866) 212-1212
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Cimarex Energy Co. of ColoradoDec 10, 2008 |
- 11,300
- total depth, ft
- 4
- permits on file
- Dec 10, 2008
- last permit issued
- Aug 18, 1979
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 18, 1979
- Shut in
- —
- Plugged
- Sep 24, 1990
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| — G-14-83915 | — | — | 0 | 0 | 0 | — |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 675692-99 | Reenter | Cimarex Energy Co. of Colorado | Dec 1, 2008 | Dec 10, 2008 | — | 11,150 |
| 212608-99 | Recompletion | Baker & Taylor Drilling Co. | Jun 23, 1983 | Jul 21, 1983 | — | 10,500 |
| 89899-99 | Recompletion | Baker & Taylor Drilling Co. | Jul 16, 1980 | Jul 16, 1980 | — | 10,500 |
| 36424-99 | Drill | Baker & Taylor Drilling Co. | Oct 30, 1978 | Oct 30, 1978 | Feb 11, 1979 | 11,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 18, 1979 | The Mother Bear G-14-83915 | Shreikey (Morrow) | Chevron U. S. A. Inc. | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,956 | 10,970 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,800 | 11 | 1,500 S |
| 2.875 | 10,800 | — | — |
| 5.5 | 11,150 | 7.875 | 450 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | Sep 7, 1979 | — |
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.
- Wellbore filings for 42-393-30644 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-393-30644 → scanned completion filings
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/39330644, documented in the API reference.