WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of B.M.T. a #23 (42-479-39740)

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof B.M.T. a #23 (42-479-39740)Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

16 LOG FILES ON 15 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
B.M.T. a #2342-479-39740Webb, TX · Hilcorp Energy CompanyhereRESISTIVITYTIFF5,432 to 8,622Feb 24, 2010run Feb 13, 2007
Benavides Gloria BMT a #742-479-39221Webb, TX · Hilcorp Energy Company0.37COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF7,963 to 8,717May 28, 2009run Jan 19, 2006
B.M.T. a #1242-479-39024Webb, TX · Hilcorp Energy Company0.41COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF7,626 to 8,642Oct 23, 2008run Jun 24, 2005
B.M.T. a #1842-479-39561Webb, TX · Hilcorp Energy Company0.55RESISTIVITYTIFF810 to 8,866Dec 9, 2009run Nov 20, 2006
B.M.T. a #2142-479-39562Webb, TX · Hilcorp Energy Company0.66RESISTIVITYTIFF7,861 to 8,842Jan 6, 2010run Dec 17, 2006
Benavides Gloria BMT a #642-479-39563Webb, TX · Hilcorp Energy Company0.81RESISTIVITYTIFF5,500 to 7,613Apr 27, 2010run Apr 15, 2007
Benavides Gloria BMT a #642-479-39563Webb, TX · Hilcorp Energy Company0.81RESISTIVITYTIFF6,950 to 8,506Apr 27, 2010run Apr 27, 2007
B.M.T. a #1742-479-39386Webb, TX · Hilcorp Energy Company0.82COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF7,732 to 8,820May 28, 2009run Mar 17, 2006
B.M.T. #18942-479-38953Webb, TX · Hilcorp Energy Company0.88COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF7,802 to 8,669Jul 18, 2008run Jan 28, 2005
B.M.T. a #1942-479-39532Webb, TX · Hilcorp Energy Company0.98COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF7,940 to 8,820Aug 21, 2009run Aug 12, 2006
B.M.T. a #1642-479-39411Webb, TX · Hilcorp Energy Company1.29COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF7,987 to 8,825May 28, 2009run Mar 14, 2006
B.M.T. a #3442-479-40709Webb, TX · Hilcorp Energy Company1.55RESISTIVITYTIFF7,726 to 10,630Feb 21, 2011run Dec 23, 2009
B.M.T. a #2942-479-40345Webb, TX · Hilcorp Energy Company1.57RESISTIVITYTIFF7,828 to 8,866Nov 29, 2011run Nov 3, 2008
B.M.T. B #742-479-38470Webb, TX · Hilcorp Energy Company1.75SURVEYS CASED HOLETIFF8,000 to 10,530Aug 4, 2008run Sep 11, 2003
BMT B TR5 #1142-479-39866Webb, TX · Hilcorp Energy Company1.93RESISTIVITYTIFF3,000 to 6,353Jul 20, 2010run Jul 28, 2007
B.M.T. a #2642-479-39758Webb, TX · Conocophillips Company1.98NEUTRON/DENSITY POROSITYTIFF8,059 to 8,808Apr 27, 2010run Apr 5, 2007

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.