WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 3 mi of API 42-331-31663

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 API 42-331-31663Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Pearson C #142-331-34452Milam, TX · Allied Operating Texas LLC1.24NEUTRON POROSITYTIFF0 to 1,477Oct 14, 2015run Sep 11, 2012
Pearson C #142-331-34452Milam, TX · Allied Operating Texas LLC1.24RESISTIVITYTIFF57 to 1,806Nov 2, 2015run Aug 16, 2012
Pearson W.T. #1B42-331-33646Milam, TX · Trustar Operating Company Inc.1.65NEUTRON POROSITYTIFF270 to 486Nov 12, 2009run Apr 9, 2009
Pearson W.T. #7B42-331-33655Milam, TX · Trustar Operating Company Inc.1.68NEUTRON POROSITYTIFF0 to 567Nov 10, 2009run Apr 3, 2009
Pearson W.T. #11B42-331-33659Milam, TX · Trustar Operating Company Inc.1.68RESISTIVITYTIFF250 to 543Nov 10, 2009run Apr 9, 2009
Pearson W.T. #6B42-331-33651Milam, TX · Trustar Operating Company Inc.1.69NEUTRON POROSITYTIFF270 to 557Nov 13, 2009run Apr 3, 2009
Pearson W.T. #6B42-331-33651Milam, TX · Trustar Operating Company Inc.1.69NEUTRON POROSITYTIFF280 to 544Nov 13, 2009run Apr 3, 2009
Pearson W.T. #5B42-331-33650Milam, TX · Trustar Operating Company Inc.1.71NEUTRON POROSITYTIFF280 to 555Nov 10, 2009run Apr 3, 2009
Pearson W.T. #4B42-331-33649Milam, TX · Trustar Operating Company Inc.1.72NEUTRON POROSITYTIFF260 to 541Nov 10, 2009run Apr 3, 2009
Pearson W.T. #3B42-331-33648Milam, TX · Trustar Operating Company Inc.1.75NEUTRON POROSITYTIFF300 to 530Nov 12, 2009run Apr 3, 2009
Clark #242-331-34898Milam, TX · Allied Operating Texas LLC2.16NEUTRON/DENSITY POROSITYTIFF1,642 to 2,154Feb 1, 2016run Feb 1, 2013
John Von Gonten #342-331-34906Milam, TX · Von Gonten John Scott2.35NEUTRON/DENSITY POROSITYTIFF110 to 824Feb 1, 2016run Aug 20, 2014
John Von Gonten #342-331-34906Milam, TX · Von Gonten John Scott2.35RESISTIVITYTIFF40 to 824Feb 1, 2016run Aug 20, 2014
John Von Gonten #242-331-34905Milam, TX · Von Gonten John Scott2.38NEUTRON/DENSITY POROSITYTIFF50 to 662Feb 1, 2016run Aug 24, 2014
John Von Gonten #242-331-34905Milam, TX · Von Gonten John Scott2.38RESISTIVITYTIFF50 to 662Feb 1, 2016run Aug 24, 2014
John Von Gonten #142-331-34904Milam, TX · Von Gonten John Scott2.70NEUTRON/DENSITY POROSITYTIFF65 to 828Feb 1, 2016run Aug 22, 2014
John Von Gonten #142-331-34904Milam, TX · Von Gonten John Scott2.70RESISTIVITYTIFF100 to 828Feb 1, 2016run Aug 22, 2014
Svrcek #242-331-35101Milam, TX · Mojo Exploration & Production L2.96InductionTIFF50 to 1,996Nov 22, 2024
Rountree #b 2242-331-33688Milam, TX · Winchester Oil & Gas LLC2.99SURVEYS CASED HOLETIFF350 to 615Jan 13, 2010

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.